🛠️ How-to guide
<aside>
🛠️
WHAT IT DOES
The Advanced tab connects an agent to the outside world and shapes how it routes and responds — external APIs and databases, knowledge, other agents, telephony, rich cards, and data tables. Part of Inside Your Agent.
</aside>
Before you start
Editing Advanced needs a role that can edit agents — Editor, Publisher, or Admin (see Roles & Permissions). Some sections are marked Beta.
The Advanced tab — connect APIs, databases (Beta), RAG, MCP (Beta), and data sources; route to other agents; add telephony, cards, and table bindings (Beta).
What you can configure
- API Connections — let the agent call your external REST APIs as tools. Set a name, method, and URL; add authentication (none or OAuth 2.0), headers/body, and which part of the response to use. Store secrets as workspace secrets with
{{kv:secret-name}} rather than pasting them in.
- SQL Connections (Beta) — let the agent run a read-only lookup against your database. Provide a connection string (use a read-only user), a single parameterized
SELECT, and its parameters.
- RAG Connections — point the agent at a RAG Projects for retrieval. Add a routing rule (when to use it), a suggested-actions mode, and whether the agent can paraphrase the result.
- MCP servers (Beta) — connect external MCP tool servers by URL, with an optional auth token.
- Data Sources — add inline Q&A or text sources the agent can draw on, with an option for verbatim answers.
- Multi-Agent Rules — route to other agents, either interactive (takes over the conversation) or autonomous (runs in the background and reports back). See Multi-Agent & Routing.
- Human Escalation — enable handoff to a live-agent system and choose whether to send a transcript. Full setup in Inside Your Agent → Human Escalation.
- Telephony — Transfer (to an E.164 number, with a pre-transfer message) or Hangup actions for voice calls, with rules for when to trigger them.
- Cards — rich cards the agent can show (basic, hero, or adaptive) with a title, body, image, and buttons.
- Table bindings (Beta) — control whether and how the agent renders data tables in web chat: Off, Dynamic (the agent composes them), Workspace tables (exact values from your data), or Both — with per-table access (read / add / update), a pinned filter, and visible columns.
Prerequisites at a glance
| To use… |
You'll need… |
| API Connections |
A reachable API URL and, if protected, OAuth credentials (stored as secrets). |
| SQL Connections (Beta) |
A read-only connection string and a single SELECT query. |
| RAG Connections |
An existing RAG project in the workspace. |
| Multi-Agent Rules |
At least one other agent in the workspace. |
| Table bindings (Beta) |
At least one workspace data table. |
FAQ
- How does the agent use an API connection? It calls it as a tool when the conversation needs it — you describe when and how in the connection.