---
title: "Build a conversation flow"
description: "Connect conversation, logic and action nodes inside an agent."
url: "https://documentation.verbatik.com/conversation-flow/"
---

# Build a conversation flow

Connect conversation, logic and action nodes inside an agent.

## Agent flow or Deploy Flow?
An agent's **Conversation flow** controls steps within a conversation. **Deploy → Flows** schedules work across leads, calls and SMS, such as calling a new lead after ten seconds. They are separate builders. See [Deploy Flows](/deploy/flows/) for automation between conversations.

## Build the graph
1. Create a **Conversation flow** agent or open an existing one.
2. Add nodes from the left palette.
3. Select a node to edit **Node settings**. Keep shared instructions in **Global settings**.
4. Connect each transition to its intended destination. Give branches clear conditions.
5. Provide an ending and a fallback route for missing data or failed actions.
6. Save and test every branch before publishing.

## Node types
| Node | Purpose |
| --- | --- |
| Conversation | Speak and collect the caller's response. |
| Logic split | Route using configured conditions. |
| Extract variable | Capture structured values for later steps. |
| Function / MCP | Execute an approved bound tool. |
| Subagent / Agent transfer | Delegate to an authorized agent. |
| Call transfer | Hand the phone caller to an approved destination. |
| Press digit | Send keypad digits on a supported phone transport. |
| In-call SMS | Request a message when the sender, recipient and permissions allow it. |
| Code | Transform variables with isolated JavaScript. Network, files, credentials and imports are unavailable. |
| Ending / Note | Finish the conversation or annotate the graph. |

A visual node does not establish external access. Bind the corresponding tool, published target agent or transfer destination first. Exercise failure branches with a browser test where possible, then validate carrier-only behavior with an authorized phone test.