Integrations
Integrations connect external systems to your workspace so agents can use them as tools during calls: calendars, email, your own APIs, or any MCP server.
These types are available today:
| Integration | Use it for |
|---|---|
| Google Calendar | Check availability and book, move, or cancel appointments. |
| Calendly | Check availability and book or cancel Calendly appointments (paid Calendly plan required to book). |
| Cal.com | Check availability and book, reschedule, or cancel Cal.com appointments (cloud or self-hosted). |
| Acuity Scheduling | Check availability and book, reschedule, or cancel Acuity appointments. |
| Cliniko | Check availability and book, reschedule, or cancel Cliniko appointments (allied-health clinics). |
| Square Appointments | Check availability and book, reschedule, or cancel Square appointments (Appointments Plus/Premium plan required to book). |
| Mindbody | Check availability and book, reschedule, or cancel Mindbody appointments and classes (fitness studios, gyms, salons, spas; partner application required). |
| Resend | Send emails from your own domain using your Resend account. |
| Webhook / HTTP | Let the agent call your own API endpoints (host allowlist). |
| Custom MCP server | Connect any remote MCP server by URL and expose its tools. |
Adding an integration
On the Integrations page, click Add integration, pick the type, and
give it a name. The name matters: tools are exposed to your agents
prefixed with a slug derived from it. An integration named “Booking calendar”
exposes tools like booking_calendar_list_events.
Each type then asks for its own configuration — see the pages above for details. Google Calendar and Square Appointments continue to an OAuth sign-in (Google / Square); the other types discover their tools immediately after you save.
Tool discovery
Discovered tools are cached per integration and shown as badges on the integration card. If the upstream tools change (for example you redeploy your custom MCP server), click Refresh tools to re-discover. Agents and live calls use the cached list, so a temporarily unreachable upstream never hides known-good tools mid-call.
Using integration tools in an agent
Integration tools are enabled per agent version, in the Integration tools card of the agent builder. Like everything else in the builder, the selection is part of the draft and goes live when you publish.
Security
- Credentials (API keys, OAuth grants, bearer tokens, secret headers) are encrypted per workspace and never shown again after you save them — and never exposed to the agent, the model, or the browser.
- During a call, integration tools are executed server-side by Ciaomatic; the agent only sees the tool’s result.
- Every invocation is recorded in the per-call tool audit.
Status
Each integration card shows Connected, Pending setup (e.g. waiting for the Google sign-in), or Error (with the last error message). Deleting an integration removes its stored credentials; agents lose its tools on their next call.