Theme
CX Agent Studio Node
The CX Agent Studio node integrates with a CX Agent Studio (CES) deployment, enabling your flow to delegate conversation handling to a CES agent. The node supports session management, sub-agent routing, variable passing, and automatic tool invocation.
When to Use
- You have an existing CX Agent Studio deployment with specialized agents and tools.
- You want to delegate complex conversation logic to a CES agent while keeping the overall flow in OmniBots.
- You need multi-turn interaction with a CES agent within a single flow node.
- You want to route to a specific CES sub-agent based on conversation context.
Configuration
| Property | Description | Default |
|---|---|---|
| CX Agent Studio Integration | The CES integration configured in your workspace. | None (required) |
| Entry Agent / Sub-Agent | Route to a specific sub-agent. Leave empty to use the root agent. Dropdown is populated dynamically from the CES API. | Root Agent |
| Session Variable | Session variable to track the CES session ID across turns. | cx_session_id |
| Query Variable | Variable containing the query text. Leave empty to use the user's latest message. | Empty |
| Send Agent Response to User | Automatically send the CES agent's response to the user. | true |
| Pass Variables | Flow variables to pass as extra parameters to the CES agent. | Empty |
Output Variables
| Property | Description | Default |
|---|---|---|
| Response Variable | Variable to store the CES agent's response text. | cx_response |
| Active Agent Variable | Variable to store which sub-agent handled the response. | cx_active_agent |
| Tool Calls Variable | Variable to store tool calls made by the agent (optional). | Empty |
Handles
| Handle | Direction | Description |
|---|---|---|
| Input | In | Receives execution from the previous node |
| Success | Out | The CES agent responded successfully |
| Error | Out | An error occurred communicating with the CES agent |
| Handoff | Out | The CES agent requested a handoff to a live agent |
How It Works
- When the node executes, it sends the query to the CES deployment.
- The CES agent processes the query, potentially calling tools and sub-agents.
- The response is stored in the configured output variables.
- If "Send Agent Response to User" is enabled, the response is automatically sent to the user.
- Execution follows the appropriate output handle based on the outcome.
CX Agent Studio node config panel showing CES integration selector, entry agent/sub-agent dropdown populated from the CES API, session variable input, query variable field, send response toggle, and pass variables list
TIP
The sub-agent dropdown is populated dynamically when you select a CES integration. If you do not see agents in the dropdown, verify that your integration credentials are correct and that the CES deployment is accessible.
WARNING
CX Agent Studio sessions are stateful. The session variable tracks the session ID so that subsequent turns within the same conversation continue the same CES session. Do not clear this variable mid-conversation unless you want to start a new CES session.