Conversational Flows
Directed node graphs that define what your virtual being says and does in response to user input.
The Main Conversation Logic
Flows sit one layer below Handlers in the Pipeline and are activated by them – or by other flows. Once activated, execution begins at the Flow Entrypoint node and moves through the connected nodes until it reaches a terminal node.
Flow Types
When you create a new flow you choose its type. The type determines which nodes are available on the canvas. There are three types.
Custom
The standard flow type for building conversation logic manually. Custom flows have access to the broadest set of nodes across all categories:
| Category | Nodes available |
|---|---|
| Response | Text, LLM Response |
| Action | Open Web View, Quick Reply, Collect User Data, Cards from Table, and others |
| Context | Check Variable, Store Variable, Create title, Create summary, Extract variables, Find Records |
| Language | Change Language, Accept Language Change, Reject Language Change |
| Integration | Call Webhook, Custom Action, Call Conv AI |
| Logic | Route by Profile, Route by Language, Route by Signal, If/Else Router, Is Flow Active, Intent Matcher |
| Flow | End conversation, Go to Flow |
| Other | Comment |
Use Custom flows for anything that involves responding to users, collecting data, calling APIs, or building conditional branching logic.
Agent
Agent flows are purpose-built for the Tool Agent node. The node palette is intentionally limited to keep Agent flows focused:
| Category | Nodes available |
|---|---|
| Agent | Tool Agent |
| Other | Comment |
Because Agent flows rely on the Tool Agent to handle conversation logic internally, traditional response and routing nodes are not available. Instead, Agent flows expose an Add Tool menu where you configure what the Tool Agent can call:
| Category | Tools available |
|---|---|
| Context | Store Variable |
| Flow | End Flow, Go to Flow, Trigger Automation |
This keeps the flow canvas clean – a single Tool Agent node with its tools configured inside it, rather than a sprawling node graph.
Automation
Automation flows are designed for background or triggered processing rather than direct conversation turns. They have a reduced node set:
| Category | Nodes available |
|---|---|
| Response | Text, LLM Response |
| Context | Check Variable |
| Logic | Route by Profile, Route by Language, Route by Signal, If/Else Router |
| Flow | End conversation, Go To Flow |
| Other | Comment |
Use Automation flows for logic that runs in response to a Trigger Automation tool call from an Agent flow, or for lightweight background branching that doesn't need to produce user-facing output directly.
Pre-existing Flows
New pipelines include two special flows that are created automatically and cannot be deleted: Core and Main. These define the default conversation routing path.
Core
Core is the entry point for all conversational turns. Every user message flows through Core first, before anything else. It is a restricted flow type – the node palette contains only routing and logic nodes:
| Category | Nodes available |
|---|---|
| Context | Check Variable |
| Logic | Route by Profile, Route by Language, Route by Signal, If/Else Router |
| Flow | End conversation, Go to Flow |
| Other | Comment |
Core's job is to inspect the incoming turn and route it to the right flow – by language, by profile, by signal, or by condition. By default, Core routes to Main for standard conversational turns.
The default execution path is: Core → Main → …. Core handles global routing; Main handles the conversation.
Main
Main is the default destination for turns that Core does not route elsewhere. It behaves exactly like a Custom flow – the full node palette is available. By default, Main is where the primary conversation logic lives (routing to Agent flows, responding to users, etc.).
You can restructure Main freely, or route most traffic from Core to other flows and keep Main as a fallback.
The Flow Sidebar
All Conversational Flows are listed in the left sidebar of the Conversation Editor under Conversational Flows. Click any flow name to open it on the canvas. The sidebar shows the number of flows currently in use out of the maximum (e.g., Flows used: 3/20). The maximum number of flows depends on the licence.
Flows you create yourself appear below Core and Main. Each user-created flow has a three-dot menu (⋮) for renaming or deleting.
Adding a New Flow
- Scroll to the bottom of the Conversational Flows section in the sidebar
- Click + Add flow
- Enter a Name for the flow
- Select a Type: Agent, Custom, or Automation
- Click Create
The new flow opens on the canvas with a Flow Entrypoint node already placed.
Flow Entrypoint
Every flow starts with a Flow Entrypoint node. It is added automatically when a flow is created and cannot be deleted. It has two output ports:
- On User Input – connects to the first node that processes an incoming user message
- On Signal – connects to nodes that handle a signal firing while this flow is active
Reusable Sub-flows
Any flow can be called from another using Go to Flow, and control returns to the calling flow when the called flow reaches End Flow. This lets you build shared sub-flows – for example, a GDPR consent check or a "contact human" sequence called from multiple entry points.
End Flow returns to the calling flow. End conversation terminates the entire session – use it only when you intend to end the interaction, not to exit a sub-flow.