A chatbot anyone can talk to (conversational flow)
The conversation from the original request, built as a flow: a public menu (information / product information / discounts), and behind product information a second menu (Software / Hardware) where Software answers with a picture and then looks the current release up in a database and says it back. Every reply is one HTTP call, and the same flow answers over MCP as two tools. It also carries the other half of the story: 'my account' is marked sensitive, so reaching it re-asks for the customer's PIN even in the middle of a conversation that was already signed in.
Connects to
- SQLite
Also includes
- Chat flow
- 2 pipelines
How you know it worked
Run the demo's pipeline once to create the product table. Then open the flow in Chat flows → demo-support-bot and press Try it: reply 2, then 1, and the bot shows the software picture and the release it just read from the database. Reply 4 from the main menu and it asks for a PIN first — that is the sensitive branch. Over HTTP the same conversation is POST /chat/dev/demo-support-bot: post {} to start, then post the sessionId it returns with {"reply":"2"}.
Try this templateUsed in: Insurance & brokerage
Related templates
Publish a pipeline as a public API
The same pipeline shape as everything else, reachable over HTTP: a slug, a declared parameter, and a synchronous response that hands the caller…
Parallel checks joined into one published decisionOnboarding checks as one decision call
The tabs an onboarding officer opens by hand — the identity service on one, the credit bureau and its watchlist flag on another — as one published…
Stop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.