Skip to main content
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

Vapi

API key plus a webhook URL you paste into Vapi.

Retell

API key plus a webhook URL you paste into Retell.

Speechify

API key plus a per-agent webhook URL you set in Speechify.

Telnyx

API key to import your Telnyx AI voice assistants.

Cartesia

API key to connect your Cartesia voice-agent account.

LiveKit

Forward each finished session from your LiveKit Agents worker.

ElevenLabs

API key plus a post-call webhook you add in ElevenLabs, with hourly pull as backup.

Custom & other providers

Bland, Pipecat, or any in-house stack — mint a key and POST calls.
Not sure which to pick? See Connect a voice provider.

​
Telephony enrichment

Alongside your voice provider — not instead of it.
  • 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.

​
Notifications

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

​
Issue tracking

  • 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 — 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.
  • Onboard with an agent — have that connected editor connect a provider, create a monitor, and route findings for you.