Tools, MCP and approvals
Assign versioned operations, connect your organisation's accounts and authorize actions explicitly.
A tool gives the assistant a specific operation. Use Build → Tools for reusable definitions and the assistant's Tools tab for assignment. Connect the required integration in your organisation.
Choose and configure a tool
- Choose an available published tool, or create an organisation tool for an available integration.
- Define its purpose and input JSON Schema, including required fields and allowed values. Keep fixed server values in the definition and credentials in Integrations.
- Configure operational messages and conditions such as required caller fields or completion phrases.
- Use the simulator to check inputs and conditions without an external request. Publish the definition when ready.
- Assign its published version in the assistant's Tools tab, Save, and test approval, decline and failure.
- Publish the assistant for the customer channel.
Available operations include configured HTTP requests, supported native integration actions, installed MCP operations and call controls. Availability in your workspace does not mean every operation is permitted on every public channel.
Use installed MCP operations
Connect an available shared MCP integration with your organisation's credentials. Select individual installed operations. Remote HTTP/SSE connections are supported; local stdio commands and automatic OAuth login/refresh are not.
A changed remote schema can invalidate an older contract. Request a reviewed catalog update, then review the available operation and republish. Tools are never discovered or enabled automatically for a caller.
Approve an action
Read operations can run without approval only when their execution policy permits it. Writes and approval-required operations present action details. Browser callers choose Approve action or Decline; telephone callers say approve action after hearing the summary.
Approvals bind to one call and argument set, expire after 40 seconds and are consumed once. A model claiming consent cannot authorize an action. API Request tools require explicit approval, including GET requests.
Handle uncertain results
Review status in Logs. Ending a call cancels pending approval, but a dispatched request can still complete externally. An unknown result is not automatically retried; check the destination before trying again.
For ordered intake and actions, use a conversation flow. Validated knowledge still performs evidence checks for factual answers alongside actions.