π οΈ How-to guide Β· Last updated: October 1, 2026
<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, tools from services like Cal.com or Notion, other agents, telephony, rich cards, data tables, and the documents the agent can hand out. 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 on the Riverton 311 agent: Integrations (API, SQL, RAG, MCP Connections, Data Sources), Routing, and Analytics & Content, including the new Document generation. MCP Connections is open, with Cal.com and City Permits connected.
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 Connections (Beta) β give the agent tools from services such as Cal.com, Notion, or Stripe. Pick a service from the built-in library (or enter a server address), then sign in with the provider or add a key. See MCP Connections.
- 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.
- Document generation (Beta) β name the files the agent can hand people in web chat β PDF, Word, Excel, calendar invites, QR codes, and more. See Document generation.
<aside>
β TIP
Never paste API keys or database passwords directly β store them as workspace secrets and reference them with {{kv:secret-name}}. The runtime handles the rest, and your credentials stay out of the agent's configuration.
</aside>
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. |
| MCP Connections (Beta) |
An account with the service, or its MCP server address and a key. |
| Document generation (Beta) |
A web chat channel, where the files are delivered. |