Skip to content

Provider Matrix ​

When you connect a provider, for example your Plivo account so your agent can send SMS, Perfox sends through your account, not a shared one. This page lists every provider you can connect, the fields each one asks for, what Perfox runs for you, and the webhook address each two-way provider needs.

Jump to what you need:

The Connections page in Perfox Studio, with a slot for each provider grouped by category

Bring Your Own Provider ​

For the services your agents talk through (phone numbers, messaging apps, email accounts, your own storage and databases, Google Sheets) you bring your own account and Perfox uses your keys. Keys are encrypted when saved and stay in your workspace.

There's no default account or sender. Every message leaves from a number or address one of your agents is linked to, through the connection that owns it. If a connection is missing, a required field is blank, or no connection owns the sender, the send stops with a message that names the provider to fix. Nothing fails silently. More on this model: Bring Your Own Provider.

What you can connect ​

Open Admin → Connections. The page shows one slot for every provider you can connect, grouped by category, whether or not you've set it up yet:

  • Not configured: the slot shows Connect (Connect with Google for Google Sheets and Gmail, Connect Microsoft for Microsoft 365).
  • Connected: each connection gets its own card with Test Connection, Edit, delete and expand, plus Add another <provider> below it.

The button opens a window for that provider only, titled Connect <provider>, so you can't pick the wrong type by mistake. Full walkthrough: Connections.

Telephony & Messaging ​

ProviderWhat you enterGuide
Plivo (WhatsApp, SMS, Voice)Auth ID and Auth Token. Optional: SIP domain, username and password; India SMS DLT entity ID, template ID and template category; WABA ID for WhatsApp template sync. You tag phone numbers after saving.Plivo

Messaging apps ​

Your own bot or app on each messaging platform. Customers message it there, and your agents answer there.

ProviderWhat you enter
Telegram botBot token from @BotFather.
Slack appBot User OAuth Token and Signing Secret.
Facebook MessengerPage access token and App Secret.
Instagram DirectPage access token (for the Page linked to the Instagram account) and App Secret.
Microsoft Teams botMicrosoft App ID and client secret. App Tenant ID only for a single-tenant bot.
Discord appBot token and Public Key.
Google Chat appCloud project number and service account key (JSON).
RCS Business MessagingAgent ID, service account key (JSON) and a webhook client token you choose. Billed per message.

For these, Test Connection connects the app. Telegram is wired up automatically, and the other apps get a Webhook URL to paste into their own console. The card then names the connected bot or page. If the app's token stops working, the card turns Error and says why. Per-app setup: Messaging apps.

Email ​

Nine providers, all able to send, receive and thread replies:

ProviderWhat you enter
ResendAPI key, from email. Optional inbound signing secret and inbound address.
AWS SESAccess key ID, secret access key, region, from email (verified identity).
SendGridAPI key, from email. Optional from name, data residency, inbound parse hostname.
PostmarkServer API token, from email, message stream. Optional inbound webhook secret.
MailjetPublic API key, secret key, from email. Optional from name, parse route address.
MailgunPrivate API key, sending domain, region, from email. Optional webhook signing key.
Gmail / Google WorkspaceYour own Google app's OAuth client ID and secret, then sign in with Google.
SMTP / IMAPSMTP host, port, username, password and from email for sending; IMAP host, port, username and password for receiving.
Microsoft 365 (Email)Your own Microsoft Entra app's directory ID, application ID and client secret, either app-only (pick a mailbox) or signing in as a user.

Receiving works differently per provider. AWS SES is the one exception to self-serve receiving: Perfox receives SES email on its own receiving service, and you contact Perfox support to connect your address. See AWS SES and the full comparison in Email Providers.

Storage (knowledge-base sources) ​

These are your file stores that the Knowledge Base can sync from. They're not where Perfox keeps your files.

ProviderWhat you enter
AWS S3Access key ID, secret access key, region.
Microsoft 365 (OneDrive / SharePoint)Your own Microsoft Entra app, either app-only or signing in as a user.
Google DriveService account JSON.

Databases ​

Your own external databases, which an agent can query through a database action:

ProviderWhat you enter
PostgreSQLHost, port (default 5432), database, user, password, SSL mode (disable · require · verify-full), optional SSL CA certificate.
MySQLThe same fields, port default 3306.
MongoDBA connection string (mongodb:// or mongodb+srv://), or host, port (27017), database, user, password, auth source (default admin) and TLS.

Details: Database Connectors.

Integrations ​

ProviderWhat you enterGuide
Google SheetsYour own Google app's client ID and secret, then Save & Connect Google.Google Sheets

Only the providers above are offered. Integrations you add from MCP Registry → Popular Integrations are managed there and don't appear on the Connections page.

Included and managed by Perfox ​

Some services are part of Perfox itself. You never enter keys for them, and they don't appear as slots on the Connections page. Where model providers used to be, the AI & Search heading now shows a short note saying model keys are managed by Perfox. If you want your agents to run on your own model provider account (for example your own Gemini or OpenAI key), contact Perfox support.

ServiceWhat it doesWhat you control
AI models (text and voice)Your agents' replies, speech recognition and speech, plus built-in features such as knowledge-base indexing, summaries and "Ask AI".Which model and voice an agent uses, on its Chat Model node. See Chat Model.
File storageHolds uploaded files, knowledge-base documents and call recordings.How long data is kept, under data retention in Settings.
Knowledge-base searchFinds the passages in your Knowledge Base that are relevant to each question.What you upload and how the agent uses it. See Knowledge Base.
Web voiceCarries voice calls started from the chat widget in a browser.Turning voice on for an agent. Phone calls use your own Plivo numbers instead.

Usage of these services is paid for from your workspace's prepaid credits.

Inbound webhook addresses ​

Two-way providers need a Perfox address pasted into the provider's own dashboard so incoming messages and calls reach your workspace. Every address uses your workspace's API address:

text
https://<your-workspace>-api.perfox.ai

Use your own workspace name, the one in your Studio address. A request sent to any other address never reaches your agents.

ChannelMethod and pathNotes
SMS (Plivo): incomingPOST /webhooks/sms/plivoPlivo Message URL
SMS (Plivo): delivery statusPOST /webhooks/sms/plivo/statusPlivo Delivery / Status URL
WhatsApp (Plivo): incomingPOST /webhooks/whatsapp/plivoSet per number in the Plivo console. Plivo has no API for this, so it's always a manual step.
WhatsApp (Plivo): delivery reportsPOST /webhooks/whatsapp/plivo/statusPlivo Delivery Reports URL
Voice (Plivo): incoming callsPOST /plivo/inbound-answerPlivo Application Answer URL. Set up voice & SMS on the number can do this for you.

The Plivo editor shows these URLs already filled in for your workspace, each with a Copy button (see Point Plivo at Perfox). For outgoing calls Perfox supplies the answer URL itself, so there's nothing to set in Plivo. Messaging apps get their Webhook URL from Test Connection. Email providers that receive through a webhook show their own inbound settings on their connection (see Email Providers). Every incoming message, whatever the channel, is handled the same way once it arrives (Channels Overview).

What's next ​