Skip to main content
The Conversation Flow node embeds a Conversation Flow inside a workflow. Use it when a workflow needs a multi-turn conversation — qualifying a lead, troubleshooting an issue, walking the user through a form — and you’ve already designed that conversation as a flow.
Conversation Flow node configuration form

Conversation Flow configuration — pick which flow to start, then wire action/event handles to react to messages and lifecycle events.

​
When to use

  • Mixed mode — A workflow handles the deterministic steps; a conversation flow handles the open-ended chat.
  • Lead capture inside a pipeline — Trigger a sales triage conversation, then continue with downstream CRM updates once it ends.
  • Long-running interactions — A workflow polls, waits, or escalates while a conversation is still active.

​
How it works

  1. Pick which Conversation Flow to start. The flow must already exist in your workspace.
  2. The node opens action handles you can use to send a message into the conversation or trigger lifecycle behaviors (start, transfer, end).
  3. It also exposes event handles so the workflow can react to incoming user messages, completion, or timeouts.
  4. Each handle is wired to whatever node should run next.
This makes a Conversation Flow node feel like a sub-process: the workflow drives the conversation, and reacts to it, without leaving the workflow editor.

​
Next steps

Conversation Flows

Build the multi-agent conversation you want to embed.

Human Step

Bring one person in for an approval, a quick answer, or a sign-off.