Managing Flows
How to create, rename, duplicate, reorder, and delete Conversational Flows within the Conversation Editor pipeline.
The Conversational Flows section of the pipeline sidebar lists all flows available in your current pipeline version. Each flow appears as a named entry; clicking it opens that flow's node graph in the editor canvas.
Default Flows
Every new pipeline that is created from the default template (see more in Version Management section) contains a set of starter flows (unless you choose an option to create a blank template, which only comes with Core and Main flows):
| Flow | Default Purpose |
|---|---|
| Core | Top-level routing logic; often the first flow activated on conversation start |
| Main | Primary conversational flow for handling user input |
| Agent | A flow pre-configured to use the Tool Agent node |
| Greet | Welcome and greeting logic |
| Human Handover | Logic for escalating to a human agent |
| Signal | Example flow demonstrating signal-based routing |
These are starting points – you can rename, modify, or delete any of them to suit your use case.
Creating a New Flow
- In the pipeline sidebar, scroll to the Conversational Flows section
- 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.
Renaming a Flow
Click the three-dot menu (⋮) next to the flow name in the sidebar and select Rename. Flow names must be unique within the pipeline version.
Deleting a Flow
Click the three-dot menu (⋮) → Delete.
Deleting a flow removes all its nodes permanently. Any Go to Flow or Activate Flow nodes elsewhere in the pipeline that referenced the deleted flow will lose their connection and display a warning. Review and update these references before or after deletion.
Navigating Between Flows
Use the sidebar to switch between flows – click any flow name to open it in the canvas. The currently open flow is highlighted in the sidebar.
When a Go to Flow node is selected on the canvas, you can click the flow name to jump directly to that flow – useful for following the conversation path without hunting through the sidebar.
Organizing Flows
As your pipeline grows, keeping flows well-named and purposeful becomes important. Some recommended conventions:
- Name flows after their topic or purpose, not their position (e.g., "Product Inquiry" not "Flow 7")
- Group related flows with a shared prefix (e.g., "Order – Lookup", "Order – Cancel", "Order – Status")
- Use the Entrypoint description field to note when the flow should be triggered by an Agent
- Keep the Core flow as a lightweight router and move detailed logic into topic-specific flows