Integrations overview
Your agents already reach the world through the surfaces qRaptor builds for them: a chat widget, a Copilot, an HTTP API. Integrations are for the channels qRaptor doesn’t own — the ones that belong to somebody else and have their own rules, their own identities, and their own bill.
Today that means one thing, and it’s a substantial one: telephony. You can give a voice-enabled AI Agent a real phone number, and customers can ring it and have a conversation.
What’s here
Open Integrations in the project sidebar and you get a grid of providers grouped by category.
| Provider | Category | Status |
|---|---|---|
| Exotel | Telephony | Available — documented here |
| Frame Ingestion | Vision | Available — not yet documented |
| Twilio | Telephony | Coming soon |
| WhatsApp · Slack | Messaging | Coming soon |
| Pipelines | Pipelines | Coming soon |
| Custom Webhooks | Custom | Coming soon |
A card marked Coming Soon is a placeholder. It isn’t clickable and there’s nothing behind it yet.
Connecting to your business systems
Integrations in the sidebar is specifically about channels — surfaces that belong to someone else, like a phone network. Connecting qRaptor to the systems your business already runs happens in a few other places, and this is the full picture:
| Where | What it reaches | Set up in |
|---|---|---|
| Integrations (configurations) | Salesforce, HubSpot, ServiceNow, Jira, Slack, Microsoft Teams, Twilio, SendGrid, GitHub, Azure DevOps, AWS S3, Azure Blob, Gmail, Google Calendar, SMTP, REST API, webhooks | Configurations |
| Databases | PostgreSQL, MySQL, SQL Server, MongoDB, Redis / Valkey, Elasticsearch | Configurations |
| MCP servers | Any Model Context Protocol server — your own, or a pre-built one such as GitHub, Stripe or Notion. Tools are discovered automatically | MCP |
| App connections | Third-party services wired into a generated app, with code qRaptor writes and tests itself and credentials kept per environment | Connections |
| Custom tools | Anything with an HTTP API, as a project tool you define | Tools |
| Private systems | Internal APIs, databases and scripts that must not be exposed to the internet — reached from inside your own network | qRemoteX |
A system without a packaged connector is still reachable. If it has an HTTP API, define it as a custom tool or connect an MCP server for it; if it sits behind your firewall, run the call through qRemoteX so nothing is exposed. Credentials live in Configurations either way, never in a prompt or in generated code.
Frame Ingestion is live in the product but not yet covered here. It streams image frames — from a camera, a drone, a screen capture, a device — to an AI or Task Agent. The How to connect panel inside the product documents the streaming protocol in the meantime.
Telephony, in one paragraph
Exotel is qRaptor’s telephony provider, and it’s qRaptor-managed: there are no Exotel credentials to enter and no Exotel account to open. You pick a number from a shared pool, attach it to one of your voice agents, and qRaptor handles everything between the caller’s handset and your agent’s ears. Numbers are billed monthly in credits from your subscription.
Start at Telephony overview.
What you need
- A paid plan. Telephony is available from Starter upwards — Free and App Lite don’t include it, and the Exotel card shows an Upgrade badge instead of a link.
- A voice-enabled AI Agent that’s part of an active deployment. A number with nothing behind it still costs credits every month.
Scope — where to look instead
Two things that feel like integrations but live elsewhere:
- MCP servers — connecting an agent to an external tool server. That’s under Agent Tools.
- Content Store connectors — pulling documents in from outside sources. That’s under Data Vault → Content Store.