Skip to main content
Every conversation the assistant can hold is a flow. This screen lists them.

​
Reading the list

Each row carries more than its name. Name — with the flow’s trigger shown beneath it where one is set. The trigger is what causes this flow to start: a keyword the contact sends, or an event raised elsewhere in the platform. A flow with no trigger beneath its name is started some other way — by another flow, or as the assistant’s default. Group — the flow group it belongs to, or a dash. Groups are organisational and do not affect behaviour. Public — whether the flow can be started directly. Versions — the published version, or a dash. A dash means this flow has never gone live. It can be built, edited and saved, and contacts will never see it until it is published. The leftmost switch activates and deactivates the flow. Deactivating stops it starting new sessions without deleting anything.
Versions and the active switch answer different questions. A flow can be active and unpublished — meaning it is ready to run but has no live version to run — which is the usual state of something still being written.

​
Grouping the view

Group by re-arranges the list by any column. Once an assistant has more than a handful of flows, grouping by Group is the fastest way to find one; grouping by Versions separates what is live from what is not.

​
Creating and editing

New Flow creates one. Builder on any row opens the editor — see The flow builder. Editing never touches what contacts see. Work happens in a draft; contacts keep getting the published version until someone publishes the new one. See Publishing a flow.