One flow, called from three places (a reusable conversation)
The same verification conversation, written once and called from everywhere it is needed. A 'verify a customer' flow takes a customer code, looks it up, and hands back the account holder's name — and the main bot calls it from 'My orders', from 'Change my address', and again from 'Talk to a person'. The three callers pass an argument and read a result; none of them can see the verifier's own variables, and none of them had to copy its wording. Change the verification once and all three change with it.
Connects to
- SQLite
Also includes
- Chat flow
- 2 pipelines
How you know it worked
Run the demo's pipeline once to create the customer table. Then open Chat flows → demo-reusable-bot and press Try it: reply 1, and the bot asks for your customer code — that question, its retries and its wording live in demo-verify-customer, not here. Answer A-113 and it greets Ada Lovelace and shows the orders; reply 2 or 3 from the main menu and the same verification runs again, with a different reason in its prompt. Change the wording once in demo-verify-customer and all three branches change with it. Over HTTP the caller answers at POST /chat/dev/demo-reusable-bot; demo-verify-customer has no URL of its own, because it is marked callable.
Try this templateStop moving data by hand.
Start free with three projects, or talk to us about running it across your organisation.