Intent Router Node

The Intent Router node reads an intent variable and routes execution to the matching output handle. Each configured route creates a separate output handle on the node, allowing you to branch the flow based on classified user intent. A default handle catches unmatched intents.

When to Use

• You have classified the user's intent (via an LLM, Dialogflow CX, or the intent classifier) and need to route to the appropriate branch.
• You want visual, explicit intent-based routing on the canvas instead of chaining multiple Condition nodes.
• You need to handle multiple intent groups with a clear fallback for unmatched intents.

Configuration

Property	Description	Default
Intent Variable	The session variable containing the detected intent name.	detected_intent
Routes	A list of route definitions. Each route has a label and one or more intent names.	Empty
Default Route Label	The label for the fallback route handle.	Default

Route Properties

Each route in the list has:

Property	Description
Label	Display name shown on the output handle (e.g., "Billing", "Support")
Intents	Comma-separated list of intent names that match this route (e.g., billing_inquiry, payment_question)

Handles

Handle	Direction	Description
Input	In	Receives execution from the previous node
Per Route	Out	One output handle per configured route, labeled with the route name
Default	Out	Fallback handle for intents that do not match any route

How Routing Works

1. The node reads the value of the Intent Variable from the session.
2. Routes are evaluated in order. The first route whose Intents list contains the variable value is matched.
3. Execution follows the matched route's output handle.
4. If no route matches, execution follows the Default handle.

                            ┌── [Route: Billing] ──→ Billing branch
                            │
[Intent Router] ────────────┼── [Route: Support] ──→ Support branch
                            │
                            ├── [Route: Sales] ────→ Sales branch
                            │
                            └── [Default] ─────────→ Fallback branch

imageIntent Router node config panel showing the intent variable field, a list of route definitions with label and comma-separated intent names, and the default route label

Intent Router configuration with routes

imageIntent Router node on the flow builder canvas showing dynamic output handles labeled Billing, Support, Sales, and Default, each connected to different downstream branch nodes

Intent Router node with dynamic output handles on the canvas

TIP

The Intent Router works with any variable, not just intent classifiers. You can use it to route based on any categorical variable stored in the session.

WARNING

Always connect the Default handle to a fallback path. If the intent variable contains an unexpected value and no default path exists, the conversation will end at this node.