Integrations

Connect conversations to the systems that matter.

Use APIs, webhooks and custom tool boundaries to connect voice workflows with business data and actions.

Integration Categories

Designed around capabilities, not logo walls.

Organize connections around capabilities such as CRM, calendars, databases, automation, messaging, webhooks, APIs and custom tools.

CRM

Read or write customer context through controlled integration boundaries.

Calendar

Connect scheduling and availability logic to conversational workflows.

Database

Query application data through scoped tools rather than exposing direct database access to the model.

Automation

Trigger downstream automation from structured voice events and workflow actions.

Messaging

Hand structured outcomes to messaging systems where configured.

Webhook

Receive or emit event payloads at explicit integration points.

MCP

Represent MCP-compatible tool surfaces as one possible integration category where supported.

API

Connect application logic through HTTP-based service boundaries.

Custom Tool

Wrap business-specific actions with explicit inputs, outputs and runtime constraints.

Tool Boundary

Make external actions explicit.

A tool should expose a narrow operation with clear inputs and outputs. That keeps the voice agent connected to your application without turning the model into an unrestricted systems layer.

Defined inputs

Describe exactly what information an action requires.

Controlled execution

Keep business logic inside the application service that owns it.

Structured result

Return only the context the conversation needs to continue.

Illustrative tool boundary ILLUSTRATIVE
// Illustrative tool definition
const updateDeliveryWindow = {
  name: "update_delivery_window",
  input: { orderId: "string", window: "string" },
  execute: async (input) => app.updateWindow(input)
};

Connect voice to application logic cleanly.

Start with clear integration boundaries and connect the systems your voice workflows depend on.

Developer Overview