Skip to main content
App connections let a voice agent act inside the tools your team already uses, mid-conversation: check availability on a calendar, look up a caller in your CRM, append a lead to a spreadsheet, post a summary to Slack. You connect an account once under Connections → Apps (/dashboard/app-connections), choose what the agent is allowed to do, and attach the connection to any agent in its builder. Six applications are available today: For anything not on this list, build a custom API connection or add an MCP server.

​
Connect an account

1

Open Connections → Apps and click Add application

A picker shows the six applications. You can connect multiple accounts of the same app — each shows a “connected” count once you have one.
2

Authorize the account

Most apps use OAuth: a popup opens, you sign in to the provider and approve access, and the connection appears on the page. Cal.com is the exception — it connects with an API key instead. Paste the key and click Validate and connect; the key is checked against Cal.com before it is encrypted and saved.
3

Google Sheets only: pick the spreadsheet

A Sheets connection needs to know which spreadsheet and tab to write to. Right after connecting, a configuration panel opens — paste the spreadsheet’s URL (or its ID), click Inspect spreadsheet, and choose the tab. The panel confirms the columns it found. Until this is done the connection tile shows Needs configuration.
ThunderPhone’s Google OAuth verification is currently in review, so Google shows an “unverified app” warning during consent for Google Calendar and Google Sheets. The Add application dialog walks you through the two clicks to continue (Advanced → Go to ThunderPhone).
Connecting and managing app connections requires an admin or owner role in the organization.

​
Control what the agent may do

Every connection has per-operation permission toggles — open a connection tile to manage them. Read-style operations start enabled; operations that write to or change your data start off until you enable them: An operation you disable is simply not available to the agent — the corresponding tools are never offered to it on calls.

​
The tools your agent gets

Once a connection is attached to an agent, the enabled operations surface as callable tools during conversations:
  • Google Calendar — calendar_list_events, calendar_check_availability, calendar_create_event, calendar_update_event, calendar_cancel_event
  • Google Sheets — sheets_append_row (writes to the spreadsheet and tab you configured)
  • Slack — slack_list_channels, slack_search_messages, slack_post_message
  • HubSpot — hubspot_search_contacts, hubspot_get_contact, hubspot_upsert_contact, hubspot_add_note
  • Salesforce — salesforce_search_records, salesforce_get_record, salesforce_upsert_lead, salesforce_log_activity
  • Cal.com — calcom_list_event_types, calcom_check_availability, calcom_create_booking, calcom_cancel_booking
You don’t write schemas for any of these — ThunderPhone defines the tools and routes the calls through the connected account.

​
Attach the connection to an agent

Connections do nothing until an agent uses them. Open the agent in the builder (Build an agent) and add the connection in its Connected apps section. A connection’s tile on the Apps page shows how many operations are enabled and how many agents use it.

​
Disconnect

Open a connection tile and disconnect it from there. Agents that were using it lose those tools on their next call.

​
Next steps

Turn any API into an agent action

The paste-a-cURL wizard for services without a native connection.

Add an MCP server

Bring your own tool server over Streamable HTTP.