Skip to content

Node Connection Rules

This page documents all the rules governing how nodes can be connected in the Menu Designer.

Edge Types

Every connection (arrow) between two nodes is one of three types:

Continue Edge

The simplest connection — a linear "go to the next step" link.

Property Value
Used by Most nodes (Entry Point, Message, Question, AI Chat, Document, Image, Send Email, API Action)
Visual Arrow from the bottom of the source node to the top of the target node
Label "continue"

Routes the flow based on which option the customer selects in a Menu node.

Property Value
Used by Menu node only
Visual Arrow from the right side of a specific option to the target node
Identifier Each option's unique ID (auto-generated)

Condition Branch Edge

Routes the flow based on whether a condition is true or false.

Property Value
Used by Condition node only
Visual Two arrows from the right side — ✓ Yes and ✗ No
Branch labels yes or no

Connection Matrix

This table shows which nodes can connect to and from each other:

Source Nodes (left) → Target Nodes (top)

From ↓ / To → Entry Message Menu Question Condition AI Chat Document Image Handoff Email API
🚀 Entry ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
💬 Message ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
📋 Menu ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
📥 Question ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
🔀 Condition ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
🤖 AI Chat ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
📄 Document ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
🖼️ Image ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
👤 Handoff ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌
✉️ Email ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
⚡ API ❌ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅

Key rules:

  • ❌ Nothing connects TO the Entry Point — it has no target handle
  • ❌ Nothing connects FROM Human Handoff — it's a terminal node
  • ✅ Everything else can connect to everything else

Special Connection Rules

Entry Point

  • Must have exactly one Entry Point per flow
  • Must have at least one outgoing connection
  • Has no target handle (no incoming connections)
  • Each option gets its own output handle — connect each separately
  • Every option must be connected to a target node
  • No "continue" output — all routing goes through options
  • Different options can connect to the same target node

Condition Node

  • Has two output handles: ✓ Yes and ✗ No
  • Both should be connected (warning if either is missing)
  • Both branches can connect to the same target node
  • No "continue" output — routing goes through Yes/No branches

Human Handoff

  • Terminal node — no outgoing connections allowed
  • No "dead end" warning (this is intentional)

Loops (Cycles)

The designer allows loops (cycles) — for example, a Message that connects back to a Menu. This is a common and intentional pattern for keeping customers in a conversation.

flowchart TD
    A["📋 Main Menu"] -->|"About Us"| B["💬 About Us"]
    B -->|"continue"| A

    style A fill:#ede9fe,stroke:#8b5cf6,stroke-width:2px
    style B fill:#dbeafe,stroke:#60a5fa,stroke-width:2px

Intentional loops only

The designer detects loops and shows a warning: "The flow contains a loop. Make sure cycles are intentional." This is a warning, not an error — it won't block publishing. Just make sure the loop is deliberate and the customer has a way to exit (e.g., a "Talk to Agent" or "Exit" option).

Creating Connections

On the Canvas

  1. Hover over a node to see its handles (small circles).
  2. Drag from an output handle (bottom or right) to a target node's input handle (top).
  3. Release to create the edge.

Deleting Connections

  • Click an edge to select it, then press Delete or Backspace.
  • Alternatively, click the ✕ button that appears on a selected edge.