The canvas
Connecting steps. Drag from the dot at the right of an exit row to the dot on the left of the next step. Or, in the step editor, pick the destination in the exit’s Goes to / Next step box — easier when the two steps are far apart.
Following a connection. Each exit row on a box shows where it goes (
→ S5 Pick a day). Click it to jump to that step, wherever it is on the canvas. Open that step under every Goes to box does the same.
Disconnecting and deleting. Hover a line and click the × in its middle to disconnect it. Hover a box and click its trash icon — or select it and press Delete — to delete a step. Lines into a deleted step are left unconnected, not removed.
Hover. Pointing at a box highlights every line in and out of it.
Step numbers
Steps are numbered S1, S2, … breadth-first from Start, then the branches of each global intent, then anything not connected. The same numbers appear on the canvas, in the search, under each Test Chat reply, and in the plan the AI follows. They change when you rewire the flow — that is safe, because messages are tagged with the step itself, not its number.The step editor
Click a step to open its editor on the right. Every editor starts with a short note explaining the step type, then the step’s name — shown on the canvas and read by the AI as the step’s title, so name steps for what they do (“Ask for the email”, not “Step 4”).How a turn moves through the flow
A turn is everything the agent does in reply to one user message.Wait for the reply is the central idea. A step that waits sends its message and ends the turn: the user answers it, and the next turn continues from there. A step that does not wait runs straight into the next one, in the same turn.
So a chain like Send text → Custom function → Condition → Send template runs in one turn, and the user sees the text and the template together.
Within one turn the agent calls every function the turn needs first, then sends the turn’s messages together, in step order. If the AI sends a step that does not wait and stops there, it is told to carry on, and the turn continues to the next step.
Exact text or AI writes it
Steps that send a message — Send text, Send buttons, Ask & save, End — have two modes:- Exact text — sent word for word by code. The AI never retypes it.
- AI writes it — what you write is guidance, and the AI writes the message from it, in the conversation’s language. Use it for anything that should adapt: a greeting by name, an answer that depends on a function result, a multilingual chat.
Variables in exact text
Exact text can carry values that code fills in when it is sent:
A function result is available from the turn the function ran in onward — a template two turns later can still use it — for as long as that turn is within the history the agent reads (Context Length).
Where a value comes from
Template variables, media links, captions, file names and contact updates each take a source:
Contact attribute and Function result sources take an optional fallback, used when the value is empty. Without one, a step whose code-filled value is empty is not sent, and the AI is told why.