Flow Builder
The Flow Builder is a visual node-graph editor for scripting a deterministic conversation path, as an alternative to a free-form prompt-only agent. Use it when you need guaranteed branching logic (IVR-like) rather than letting the LLM decide freely.
Where: left nav → Flows (/flows).
Build a flow
Section titled “Build a flow”Open New Flow to enter the full-screen editor (desktop only). A blank flow starts with one Conversation node → one End node.
- Left sidebar — the node palette, Flow settings (description + a Global prompt prepended to every conversation node), and the Variables manager.
- Center — the canvas where you place nodes and draw connections.
- Right sidebar — configuration for the selected node or edge.
- Top bar — flow name, status/version, and Test, Check, Publish and Save.
Node types
Section titled “Node types”| Node | What it does |
|---|---|
| Conversation | The agent talks. Set its prompt, optionally greet on entry, capture variables from the caller’s answers, and enable custom tools / MCP servers. |
| Tool | Call a custom tool or MCP tool with templated arguments; save the response into variables; choose what happens on error. |
| Logic split | A pure branching node — its logic lives on its outgoing edges. |
| Transfer | Warm/cold transfer to a number, or transfer to another agent (terminal). |
| End | Ends the call with an optional farewell (terminal). |
Connections (edges)
Section titled “Connections (edges)”Drag from a node’s connection dot to the next node, then set the edge’s condition:
- Always — the default/fallback path.
- Rule — take this path when variable-based conditions match (equals, contains, greater than, is set, in list, …). Combine multiple clauses with All (AND) / Any (OR).
- AI decides — the agent picks the branch by meaning (only from Conversation nodes); give each branch a label describing when to take it.
Variables
Section titled “Variables”Declare variables (name, type, optional default) in the left sidebar. They’re the only names you can use in rule conditions, captures, and {{vars.X}} templates.
Test, validate & publish
Section titled “Test, validate & publish”- Check validates the flow and lists errors (which block publishing) and warnings (advisory) — click one to jump to the offending node.
- Test runs a deterministic dry-run from the start node without executing real tools, transfers or the LLM — useful to trace the Always/Rule path.
- Publish snapshots the current graph as the live version. Editing a published flow marks it “Unpublished changes” — live calls keep using the last published version until you Republish.
Start from a template
Section titled “Start from a template”If Templates are enabled, click Start from template (or open Templates in the nav) to instantiate a prebuilt flow for a vertical (municipality, clinic, restaurant, e-commerce). After creating it you get a required-secrets checklist — create any missing secrets before publishing, since the flow’s tools need them at runtime.
Assign a flow to an agent
Section titled “Assign a flow to an agent”Open the agent → Agent tab → Execution mode → Flow, then pick your flow. Only published flows appear.
- Only Conversation nodes can use “AI decides” edges — Tool and Logic-split nodes are rule/always only.
- An agent can only bind a published flow, so publish before assigning.
- In Flow mode the agent’s system prompt is ignored — the graph drives the conversation.