Theme
CX Multi-Agent Node
The CX Multi-Agent node is an advanced routing layer on top of CX Agent Studio that allows you to orchestrate multiple sub-agents within a single node. It supports three routing modes: automatic (root agent decides), manual (you specify the entry agent), and intent-based (map detected intents to specific sub-agents).
When to Use
- You have multiple specialized CES sub-agents and want to route between them based on user intent.
- You want the CES root agent to automatically decide which sub-agent to engage.
- You need to explicitly map intents from your OmniBots flow to CES sub-agents.
- You want a single node that handles multi-agent orchestration with a fallback agent.
Configuration
| Property | Description | Default |
|---|---|---|
| CX Agent Studio Integration | The CES integration configured in your workspace. | None (required) |
| Routing Mode | How to select the sub-agent: auto, manual, or intent_based. | auto |
| Session Variable | Session variable to track the CES session ID. | cx_session_id |
| Fallback Agent | The sub-agent to use when no intent matches (for intent-based mode). | Empty |
Routing Modes
Auto Mode
The CES root agent decides which sub-agent to route to based on the conversation context. No additional configuration is needed.
Manual Mode
You configure a list of sub-agents and specify which one to route to. Sub-agents are defined with:
| Property | Description |
|---|---|
| Name | Display name for the sub-agent |
| Agent ID | The CES agent/flow ID (selected from dropdown or entered manually) |
Intent-Based Mode
Map detected intents to specific sub-agents. Each sub-agent has:
| Property | Description |
|---|---|
| Name | Display name for the sub-agent |
| Agent ID | The CES agent/flow ID |
| Trigger Intents | Comma-separated intent names that should route to this sub-agent |
Output Variables
| Property | Description | Default |
|---|---|---|
| Response Variable | Variable to store the CES response. | cx_response |
| Active Sub-Agent Variable | Variable to store which sub-agent handled the turn. | cx_active_agent |
Handles
| Handle | Direction | Description |
|---|---|---|
| Input | In | Receives execution from the previous node |
| Success | Out | A sub-agent responded successfully |
| Error | Out | An error occurred during agent routing or execution |
| Handoff | Out | A sub-agent requested a handoff to a live agent |
CX Multi-Agent node config panel in intent-based routing mode showing a list of sub-agents with name, agent ID, and trigger intents columns, plus a fallback agent dropdown
TIP
Start with auto mode to let the CES root agent handle routing. Switch to intent-based mode when you need precise control over which sub-agent handles each user intent.
WARNING
When using intent-based routing, ensure that the intent variable is set before this node executes. Use an LLM Response node or Intent Router upstream to classify the user's intent.
