What is this?
External Capabilities let the agent call systems outside the platform — your own REST API, or a tool exposed by an MCP server — the same way Capabilities let it act on contacts and automations. Use this once your first agent is working and you need it to reach something the built-in capabilities don’t cover.Adding an external capability requires the
automations:edit permission. The tab only appears after the agent has been saved for the first time — save on General first.What can I do here?
Click Add External Capability and choose a Type:
After saving, each capability appears as a card. A card in the Needs login state is saved but switched off — the agent won’t use it until you edit it and add valid credentials.
How to use it
Add an HTTP Request capability
1
Open the dialog
Click Add External Capability, choose HTTP Request / Webhook, and fill in:
2
Test it (optional)
Click Test to send a real request from the dialog before saving. Fill in sample input values and read the response.
3
Save
Click Save. The capability is immediately available to this agent.
Add an MCP Tool capability
1
Open the dialog
Click Add External Capability, choose MCP Tool, and enter:
- MCP Server URL — the
https://address of your MCP server. - Authentication — if the server requires it, see Authentication below.
- Extra headers — any custom headers the server needs.
2
Fetch tools
Click Fetch tools from server. The dialog connects to the server and lists all the tools it exposes. Tick the ones you want this agent to use — a separate capability is created for each one, with its inputs and description pre-filled from the server’s own schema.If the server returns
401 or 403, the capability is saved in the Needs login state — it is off until you edit it, add valid credentials, and fetch again.If your server isn’t reachable, or you already know the tool name, you can type it manually under Type a tool name.3
Set 'When should the AI use this tool?' (single tool)
When you select exactly one tool, a When should the AI use this tool? field appears. Write a specific instruction — e.g. Use this when the customer asks to reschedule a booking. Click the sparkle icon to have AI rewrite it based on the tool’s name and inputs.When multiple tools are selected, each tool uses its own description from the server automatically. You can edit them individually after they are created.
4
Save
Click Save. Each selected tool appears as its own capability card.
Authentication
Both HTTP and MCP capabilities support the same authentication options:
Credentials are stored encrypted and never shown in call records or to the customer.
Write the “When should the AI use this tool?” field like you mean it
This one field is the entire decision surface. Vague descriptions mean the agent won’t reach for the tool reliably even when it should; a specific instruction gets matched correctly against real customer messages. Use the sparkle icon to let AI rewrite your draft.Fix a capability stuck in “Needs login”
If a capability card shows Needs login:- Click Edit on the card.
- Enter the correct token or OAuth credentials.
- Click Fetch tools from server (MCP) or Test (HTTP) to verify the connection.
- Click Save. The card changes to show the capability is connected and on.
Edit or remove a capability
Click Edit on a card to change any field. Click Remove to delete it — the agent stops using it immediately and this cannot be undone.Troubleshooting / Technical Notes
- I don’t have permission to add one. You need
automations:edit— check with your workspace admin. - The tab is empty right after creating the agent. Save the agent on General first — External Capabilities only unlocks afterward.
- The agent never calls it. Almost always the “When should the AI use this tool?” description — make it specific to a real customer request, not a generic label. Also check the capability is toggled on (visible in the card, not showing Needs login).
- Fetch tools returns “No tools found”. The server is reachable but lists no tools for your key, or the server does not implement the MCP tools/list endpoint. Check your server logs.
- Fetch tools fails with 401/403. Your credentials are wrong or missing — the capability is saved as Needs login. Edit it and enter valid credentials.
- Test says “Could not reach your server”. The URL must start with
https://and be reachable from the internet (notlocalhost). - A
{{variable}}in the URL or body is not working. Make sure a matching Input is defined — if the variable isn’t in the Inputs list, it won’t be filled in and every call will fail.