Integrations
What connects to CallAgent today, and what does not.
The list below is not typed by hand. It is read from the same two registries the console runs on, and the providers you cannot select yet are kept separate rather than mixed in with the rest.
CallAgent has 25 ready-made business integrations today, 18 transcription, model and voice providers selectable from an assistant, and 8 storage destinations for recordings. On top of those you can add your own HTTP tools and MCP servers.
Four families, each with its own number
The transcriber, the model and the voice are chosen per assistant, and a fallback chain moves to the next provider if one fails mid-call. A provider only becomes usable once you add a credential for it in your own organization.
Transcription
12What turns the caller into text in real time. The language is set per assistant — if you work in Romanian, you set it explicitly.
3 more providers seeded but not opened
Language models
5What decides what the assistant says and when it calls a tool. Includes an OpenAI-compatible provider for a model you host yourself.
13 more providers seeded but not opened
Speech synthesis
1What speaks back. Exactly one is connected end to end today; the rest have adapter code written and are not open yet.
16 more providers seeded but not opened
Telephony
1Where the call comes from. Twilio is the only path proven from number to audio; the rest are in the registry and marked as such.
4 more providers seeded but not opened
Everything that connects, on one list
Providers, business connectors and storage destinations together. Search by name or filter by category. Anything marked "planned" exists as adapter code but cannot be selected from an account yet.
Airtable
Amazon S3
Amazon S3 (STS role assumption)
Anthropic
Anthropic via AWS Bedrock
Anyscale
AssemblyAI
Azure Blob Storage
Azure OpenAI
Azure Speech
Azure Speech
BYO SIP trunk
Calendly
CallAgent platform storage
Cartesia
Cartesia
Cerebras
Cloudflare R2
Custom OpenAI-compatible LLM
Custom transcriber
Custom voice provider
Deepgram
Deepgram Aura
DeepInfra
DeepSeek
DIDWW
ElevenLabs
ElevenLabs Scribe
Freshdesk
Gladia
Gmail
GoHighLevel
Google Calendar
Google Cloud Storage
Google Gemini
Google Sheets
Google Speech-to-Text
Groq
HubSpot
Hume
Inflection AI
Intercom
Inworld
Jira
Linear
LMNT
Make
MCP server
Microsoft Dynamics 365
MiniMax
MiniMax
Mistral
Neuphonic
Notion
OpenAI
OpenAI
OpenAI Realtime Transcription
OpenAI TTS
OpenRouter
Outlook Calendar
Outlook Mail
Perplexity
Pipedrive
PlayHT
Rime AI
S3-compatible (MinIO, Wasabi, Backblaze B2)
Salesforce
Sesame
Shopify
Slack
Smallest AI
Soniox
Sonix
Speechmatics
Stripe
Supabase Storage
Talkscriber
Telnyx
Together AI
Twilio
Twilio SMS
Vonage
WellSaid Labs
WhatsApp Business
WooCommerce
xAI
xAI
xAI
Zapier
Zendesk
Zoho CRM
Nothing matches. Try another word or clear the filters — and if it is genuinely not here, your own HTTP or MCP tools cover the rest.
They sit in the application registry with maturity "not implemented", which means they appear in nobody's selection list. We show them because the adapter existing is a fact and being able to pick it is not.
If it is not on the list, you write it
Ready-made connectors cover the ordinary cases. Your internal system is not an ordinary case, so an assistant can call any HTTP service you have, with a JSON schema you define and with versioning.
And if you already have an MCP server, you connect it, see the tools it exposes, allow only what is needed and attach them to an assistant. CallAgent is also an MCP server itself.
Your own HTTP tool
A URL, a JSON schema for the arguments, a version. The assistant calls it mid-call and gets the answer back into the conversation.
A connected MCP server
Tool discovery, a permission gate per tool, and refresh. An MCP server is a URL somebody else controls, so it is treated as one.
CallAgent as an MCP server
The console exposes your organization as an MCP server, authenticated with ordinary API keys, so an MCP client can manage assistants and numbers directly.
Recordings can go to you
Eight storage destinations, all with the adapter installed in this build. You configure it once, it is checked with a real write-and-read probe, and recordings and transcripts are written there.
- platform
- s3
- s3_sts
- r2
- azure_blob
- gcs
- supabase
- s3_compatible
What people ask about integrations
How many integrations does CallAgent have?
Today there are 25 ready-made business connectors, 12 transcription services, 5 language-model providers, one speech provider and 8 storage destinations. The numbers are counted from the application registry each time the page renders rather than typed by hand, so they cannot fall behind.
Why are there providers I cannot select?
Because the adapter is written but the provider is marked "not implemented" in the registry and appears in no selection list. We would rather show the split than publish a large number that implies something else; a name you cannot pick is not an option.
Can I connect my own system?
Yes, through your own HTTP tools with a JSON schema or through an MCP server of your own. You do not need an integration written by us to connect an assistant to your CRM, your ERP or your database.
Can I use my own OpenAI or ElevenLabs keys?
Yes. Add the credential to your organization, the usage lands on your own account with the vendor, and from us you pay only the €0.10 per minute platform margin.
Notes
-
1
Providers and their maturity:
app/Services/Registry/RegistryData.php. Connectors:app/Services/Integrations/ConnectorRegistry.php. Both are read at render time throughApp\Support\Site\Inventory. -
2
Storage destinations:
app/Enums/Storage/StorageDriver.php. The list contains only the drivers whose package is installed in this build.