Integrations

Connect the tools Terri should use during a call. Tenant admins manage this on the Integrations page; other roles can view status.

Gmail and Google Calendar

Connect Gmail and Google Calendar from the dashboard. Once connected, Terri can read availability and mail context during a live call instead of promising a callback. Only a tenant admin can start or disconnect the Google connection.

Outlook Calendar

Connect Outlook Calendar from the dashboard. Once connected, booked visits are written to the owner's Outlook calendar. Only a tenant admin can start or disconnect. Signed call-event webhooks stay the generic outbound.

Connector gallery

The connector gallery lists apps you can authorize so Terri can take actions there during a call. Connected apps are scoped to your tenant. Disconnecting an app removes it from the live tool set.

Your own MCP servers

Tenant admins can register an upstream MCP server with a label, URL, optional bearer token, and an optional allowlist of tool names. Terri only calls tools you have allowed on that server.

Call event webhooks

Paste an HTTPS URL on Integrations. Terri POSTs signed JSON when a call is answered, booked, transferred, or missed. Requests include X-Terri-Timestamp and X-Terri-Signature (HMAC-SHA256 of timestamp.body). Disable or delete the URL at any time.

Zapier

Point a Zap at those same signed call events. Create a Zap with Catch Hook and paste the hook URL on Integrations. Terri POSTs JSON on answer, book, transfer, and miss. A Catch Hook is enough; a first-party Zapier app is not required.

Muse

Muse can reach this Terri account as a custom connector. Copy the MCP URL and bearer token from Integrations, then in Muse open Settings, Connectors, and ask it to connect Terri. OAuth MCP at /mcp uses terri.read, terri.act, or terri.manage. The public descriptor is /.well-known/muse-connector.json. Directory listing is submitted at muse.ai/platform and reviewed by Meta; Terri is not a first-party Muse app until that review lands.

Terri as an MCP server

OAuth-capable MCP clients can connect to Terri at /mcp using terri.read, terri.act, or terri.manage. Discovery lives at /.well-known/oauth-protected-resource. This is how another agent uses the same scoped tools the dashboard exposes.

When a tool fails

If a connected tool cannot be reached, Terri says so and stops rather than inventing an appointment, a price, or a message that was never sent. A failed tool is a stop, not a guess.