The Flow tab shows the top-level graph. In intent-first designs, each intent owns its own sub-flow; the main flow often contains a single intent entry node. Use the canvas to wire high-level routing or legacy monolithic flows.
Build for traceability
Before implementation is considered done, every node should have a clear Name, every branch should have an obvious condition, and every external dependency should be represented as a Tool or Secret instead of hidden in prose.
Canvas basics
- Drag nodes from the library onto the dotted grid.
- Connect handles to create edges; click an edge to delete or label it.
- Select a node to edit properties in the inspector (right panel).
- Every node has a Name field — used in the execution trace (mandatory for clarity).
- Changes autosave after a short debounce; use Save for an immediate write.
Node types
| Node | Purpose |
|---|---|
| Intent / Start | Entry point for a conversation path. |
| Message | Bot reply; per-channel copy and rich UI (buttons, cards, carousel, list). |
| Entity | Prompt user and capture a slot value. |
| Decision | Branch on edge conditions (yes/no or expressions). |
| Router | Multi-way branch with priority-ordered conditions. |
| Service / Tool | HTTP call with mapped outputs. |
| Python | Sandboxed script for custom logic. |
| Set | Assign a session variable. |
| Handoff | Transfer to a human agent. |
| Subflow | Invoke another flow by reference. |
| Knowledge | Retrieve chunks and optionally synthesize an answer. |
| End | Terminate the session. |
Node repair
Inspector or context menu can trigger scoped LLM repair for a single node. Requires LLM extraction configured.
Dragging a node only updates its position. Connections are preserved when you save — if edges disappear after reload, use Versions to restore a known-good draft.