> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect Zelto to your voice provider, notification channels, and issue tracker.

Integrations are configured per organization under **Settings → Integrations**.
Each one stores its credentials encrypted at rest; only the org members you've
added can decrypt them.

Start with a **voice provider** — that's how calls get into Zelto. Then wire up
notifications and issue tracking as you need them.

## Voice providers

<Columns cols={2}>
  <Card title="Vapi" href="/docs/integrations/vapi" icon="phone">
    API key with automatic call pulling; optional webhook for lower latency.
  </Card>

  <Card title="Retell" href="/docs/integrations/retell" icon="phone">
    API key with automatic call pulling; optional webhook for lower latency.
  </Card>

  <Card title="Speechify" href="/docs/integrations/speechify" icon="phone">
    API key plus a per-agent webhook URL you set in Speechify.
  </Card>

  <Card title="Telnyx AI" href="/docs/integrations/telnyx" icon="phone">
    API key to import your Telnyx AI voice assistants.
  </Card>

  <Card title="Cartesia" href="/docs/integrations/cartesia" icon="phone">
    API key to connect your Cartesia voice-agent account.
  </Card>

  <Card title="LiveKit" href="/docs/integrations/livekit" icon="phone">
    Forward each finished session from your LiveKit Agents worker.
  </Card>

  <Card title="ElevenLabs" href="/docs/integrations/elevenlabs" icon="phone">
    API key with automatic call pulling; optional signed post-call webhook.
  </Card>

  <Card title="Kapso (WhatsApp)" href="/docs/integrations/kapso" icon="whatsapp">
    API key to import WhatsApp numbers; Zelto registers the session webhook for you.
  </Card>

  <Card title="Custom & other providers" href="/docs/integrations/api-call-upload" icon="upload">
    Bland, Pipecat, or any in-house stack — mint a key and POST calls.
  </Card>
</Columns>

Not sure which to pick? See
[Connect a voice provider](/docs/guides/connect-a-voice-provider).

## Telephony enrichment

Alongside your voice provider — not instead of it.

* [Twilio](/docs/integrations/twilio) — most voice platforms place their phone
  legs over Twilio. Connect the account and Zelto adds carrier-level telephony
  traces to those calls: ring time, who hung up, packet loss and jitter, and the
  callee's carrier and country.

## Text & chat

Not voice? The same upload endpoint ingests text conversations.

* [Chatbot & text conversations](/docs/integrations/chatbot-text-conversations) —
  a chatbot or messaging agent (web chat, SMS, WhatsApp, in-app). Send the
  transcript, skip the audio.

## Notifications

Where Zelto posts updates — and, in Slack, where you chat with it.

* [Slack](/docs/integrations/slack) — OAuth, per-channel routing.
* [Google Chat](/docs/integrations/google-chat) — incoming-webhook URL.

## Issue tracking

* [Linear](/docs/integrations/linear) — OAuth. File an issue straight from a
  finding, with a link back, and sync the finding's status as the issue moves.

## AI access

* [MCP](/docs/mcp) — give Claude Code, Cursor, Codex, and other editors
  read/write access to your Zelto data over Model Context Protocol. Same API key
  model as the [REST API](/api-reference/agents/list-agents).
* [Onboard with an agent](/docs/onboarding-with-an-agent) — have that connected
  editor connect a provider, create a monitor, and route findings for you.

## Send monitor results to your system

Use [outbound webhooks](/docs/integrations/webhooks) to send each new positive monitor result to your database or CRM. Configure destinations under **Settings → Integrations → Webhooks**, verify a test, and deduplicate received events by their event ID. These per-call `monitor.matched` events are separate from weekly aggregate report webhooks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.