Supported integrations

For

Company admins and integration developers

Owner

Integration operations

Outcome

Connect, test, monitor, rotate, or disconnect a supported provider safely.

Last verified

2026-08-30

Next review

2026-11-28

Status

supported

Customer journey

Connect communications and integrations

Estimated time

15 min

Permissions and roles

Company admin · Integration developer

Open the completion checklistSteps, proof, and recoveryClose checklist

Prerequisites

• Company admin access
• An approved provider account
• A named owner for testing, monitoring, recovery, rotation, and disconnect

Permissions in practice

• Company admin: configure the provider and workspace connection.
• Integration developer: store credentials server-side and verify callbacks or mappings.

Steps

• Choose the supported integration group that matches the customer outcome.
• Confirm provider approval, credentials, consent, mapping, limits, and fallback ownership.
• Connect through the protected setup surface and keep the current default path safe.
• Run the provider guide with synthetic data or an approved test identity.
• Inspect health, logs, sync or callback state, and the expected healthy result.
• Record the recovery, credential rotation, disconnect, and fallback plan before activation.

Success proof

• The connection appears in the correct workspace with the expected provider and owner.
• A synthetic test produces one expected result without customer or provider traffic.
• The team can name the monitor, recover, rotate, disconnect, and fallback actions.

Common failures

• Provider approval, webhook readiness, DNS, or template approval is incomplete.
• A credential is saved in chat, browser code, logs, or an unapproved location.
• The team marks a connection active without a bounded test and recovery path.

Recovery

• Keep the current default provider or intake path active while the failed connection is repaired.
• Correct one credential, mapping, approval, or callback dependency and retest safely.

Rollback

• Pause dependent sends, calls, intake, or automation before changing a live connection.
• Switch to the documented fallback and preserve logs before disconnecting the provider.

Next task

Use the provider-specific guide for the selected connection.

Open next guide

Every published integration has a named setup surface and a safe proof path. Provider approval and availability remain provider controlled.

Use the supported registry

Open the integration that matches the customer outcome. Confirm its role, prerequisites, credentials, limits, test, recovery, rotation, and disconnect behavior before saving a secret.

• Customer intake connections: Meta lead ads, Google Ads, Google Forms, Website intake. Setup: /app/settings/lead-sources
• Company email providers: Resend, Postmark, SendGrid. Setup: /app/email/settings
• Personal email accounts: Gmail, Outlook. Setup: /app/settings?section=email
• Calendar sync: Google Calendar, Outlook Calendar. Setup: /app/settings?section=calendar
• WhatsApp Business: Configured WhatsApp provider. Setup: /app/whatsapp/settings
• Telephony providers: Exotel, MCube. Setup: /app/calls/settings/providers
• AI calling runtimes: Samvaad, Bolna. Setup: /app/calls/settings/providers
• Social and website channels: Instagram, Samvaad website chat, Samvaad website call. Setup: /app/instagram/settings
• API clients: Sakhaa Capture API. Setup: /app/api-clients

Connect safely

1. Confirm the provider account, customer owner, and required approval.
2. Store credentials only in the provider settings surface. Never put a secret in support chat or docs search.
3. Save the connection without making it the default path when the product allows this.
4. Run the documented synthetic test and inspect the expected healthy result.
5. Make the connection active only after its health and recovery path are clear.

Operate and disconnect

Review health, logs, sync state, limits, and failed work. Rotate credentials before expiry. Pause dependent sends, calls, automations, or intake before disconnecting a provider.

Do not use a real customer message, email, or call only to prove that a connection works.

Search the integration catalog

Filter the generated catalog by group, provider, role, setup path, or lifecycle action. Open the provider guide for the exact prepare, connect, test, monitor, recover, rotate, disconnect, limits, and fallback details.

Connection center

Supported integration catalog

Search by provider, group, role, setup path, or lifecycle action. Every entry is generated from the supported integration registry and links to its provider guide.

Search integrationsFilter by groupAll groupsCustomer intake connectionsCompany email providersPersonal email accountsCalendar syncWhatsApp BusinessTelephony providersAI calling runtimesSocial and website channelsAPI clients

Showing 9 of 9 supported groups.

Customer intake connections

Supported

Meta lead ads · Google Ads · Google Forms · Website intake

Customer data · 4 provider guides

DetailsClose

Prepare

An active provider source A field mapping A routing owner

Connect

Open /app/settings/lead-sources in the correct workspace and save the connection there.

Test

Use the source test action or a provider test record. Do not use customer data.

Monitor

Review connector status, source logs, duplicate results, and routing outcome.

Recover

Correct credentials or mappings, retest with a new test identifier, and review failed logs.

Rotate

Rotate the source secret in the provider and Sakhaa during the same maintenance window.

Disconnect

Disable intake first, preserve logs, and confirm where new records will be routed.

Limits

Provider approval and field availability can differ by source.

Fallback

Keep the previous approved intake source active, or route new work to a reviewed manual queue until the connection is healthy.

Role and credentials

Company admin. OAuth, webhook secret, or connector key

Provider guides

• Connect Meta lead adsCapture approved Meta lead-form submissions with the correct source and owner.
• Connect Google Ads lead captureRoute supported Google Ads lead submissions into Sakhaa.
• Connect Google FormsSend approved Google Forms responses to Sakhaa through the supported connector.
• Connect website lead intakeCapture website enquiries through the supported secret-protected intake path.

Setup route: /app/settings/lead-sources

Open setup

Company email providers

Supported

Resend · Postmark · SendGrid

Communication · 3 provider guides

DetailsClose

Prepare

A provider account An approved sending domain DNS access

Connect

Open /app/email/settings in the correct workspace and save the connection there.

Test

Use the provider test action before making the provider the default send path.

Monitor

Review provider status, default sender, domain state, webhook health, and recent failures.

Recover

Keep the current default provider active while the failed provider is repaired and retested.

Rotate

Save the replacement credential, test it, then revoke the old credential in the provider.

Disconnect

Switch the default path first. Confirm that queued and reply-tracking work will not be lost.

Limits

Automated domain management is available for Resend. Other providers use their own domain tools.

Fallback

Keep the current default provider active and use the provider failure queue until the replacement passes its test.

Role and credentials

Company admin. Provider API key and webhook secret

Provider guides

• Connect Resend emailUse Resend for approved company email sending and delivery events.
• Connect Postmark emailUse Postmark for approved company email sending and delivery events.
• Connect SendGrid emailUse SendGrid for approved company email sending and delivery events.

Setup route: /app/email/settings

Open setup

Personal email accounts

Supported

Gmail · Outlook

Communication · 2 provider guides

DetailsClose

Prepare

A provider mailbox Permission to grant the requested scopes

Connect

Open /app/settings?section=email in the correct workspace and save the connection there.

Test

Connect the mailbox and confirm the connected account appears before sending.

Monitor

Review connection, token, mailbox sync, send, and reply-threading state.

Recover

Reconnect the mailbox, then run a bounded sync if the account is healthy but stale.

Rotate

Reconnect through OAuth. Do not copy or store provider tokens manually.

Disconnect

Disconnect the mailbox and confirm the replacement send path for open work.

Limits

The provider controls consent, mailbox permissions, and token lifetime.

Fallback

Use the company send path or another approved mailbox while the user reconnects or completes a bounded sync.

Role and credentials

Signed-in user. OAuth consent

Provider guides

• Connect a Gmail mailboxConnect a user-owned Gmail mailbox for supported email work.
• Connect an Outlook mailboxConnect a user-owned Microsoft mailbox for supported email work.

Setup route: /app/settings?section=email

Open setup

Calendar sync

Supported

Google Calendar · Outlook Calendar

Productivity · 2 provider guides

DetailsClose

Prepare

A supported mailbox account Permission to grant calendar access

Connect

Open /app/settings?section=calendar in the correct workspace and save the connection there.

Test

Connect the calendar and verify one non-sensitive test event.

Monitor

Review connection state, last sync, event ownership, and time zone.

Recover

Reconnect expired consent and verify time-zone settings before resync.

Rotate

Reconnect through OAuth when the provider revokes or changes consent.

Disconnect

Disconnect sync and confirm how existing linked events will be handled.

Limits

Calendar visibility and event changes follow the granted provider scopes.

Fallback

Keep scheduling in the provider calendar and record the event owner while sync is paused.

Role and credentials

Signed-in user. OAuth consent

Provider guides

• Connect Google CalendarSync supported calendar work with the correct owner and time zone.
• Connect Outlook CalendarSync supported Microsoft calendar work with the correct owner and time zone.

Setup route: /app/settings?section=calendar

Open setup

WhatsApp Business

Supported

Configured WhatsApp provider

Communication · 1 provider guide

DetailsClose

Prepare

An approved WhatsApp business account A provider number Webhook credentials

Connect

Open /app/whatsapp/settings in the correct workspace and save the connection there.

Test

Use connection diagnostics and a provider-approved test path. Do not message a customer for proof.

Monitor

Review provider readiness, webhook delivery, templates, sync, credits, and failed messages.

Recover

Repair the failing readiness item, replay only safe inbound work, and avoid duplicate sends.

Rotate

Rotate credentials in a controlled window and rerun connection diagnostics.

Disconnect

Pause automations and outbound work before removing the provider connection.

Limits

Provider and Meta approval, template approval, and conversation rules apply.

Fallback

Pause new outbound work and route approved inbound work to the manual inbox until provider readiness returns.

Role and credentials

Company admin. Provider API key, webhook secret, and account identifiers

Provider guides

• Connect WhatsApp BusinessConnect an approved WhatsApp provider with visible template and webhook health.

Setup route: /app/whatsapp/settings

Open setup

Telephony providers

Supported

Exotel · MCube

Communication · 2 provider guides

DetailsClose

Prepare

An active provider account Approved numbers Calling and consent rules

Connect

Open /app/calls/settings/providers in the correct workspace and save the connection there.

Test

Use provider diagnostics or an approved test number. Do not call a customer for proof.

Monitor

Review provider status, numbers, webhook results, dispositions, and reconciliation.

Recover

Keep failed calls visible, repair credentials or callbacks, then run a bounded test.

Rotate

Save and test replacement credentials before the provider revokes the old pair.

Disconnect

Stop scheduled calls and confirm the fallback provider before disconnecting.

Limits

Number ownership, calling regions, recording, and carrier rules are provider controlled.

Fallback

Stop new scheduled calls and use the approved alternate provider or manual callback queue.

Role and credentials

Company admin. Provider credentials and webhook configuration

Provider guides

• Connect Exotel callingConnect an approved Exotel account, numbers, and call-status callbacks.
• Connect MCube callingConnect an approved MCube account, numbers, and call-status callbacks.

Setup route: /app/calls/settings/providers

Open setup

AI calling runtimes

Supported

Samvaad · Bolna

AI and voice · 2 provider guides

DetailsClose

Prepare

An approved provider account A configured agent A safe calling policy

Connect

Open /app/calls/settings/providers in the correct workspace and save the connection there.

Test

Use the provider test plan and an approved test number. Do not call a customer for proof.

Monitor

Review runtime status, agent mapping, number mapping, callbacks, and recent failures.

Recover

Disable the failing runtime path, preserve call evidence, and repair one dependency at a time.

Rotate

Rotate provider credentials and rerun the full runtime readiness test.

Disconnect

Pause AI calling and scheduled work before removing agents, numbers, or credentials.

Limits

Tenant activation, provider agents, numbers, consent, and runtime limits apply.

Fallback

Pause AI calling and route approved follow-up to a human owner or the reviewed non-AI calling path.

Role and credentials

Company admin. Provider API credentials and agent identifiers

Provider guides

• Connect Samvaad AI callingConnect a controlled Samvaad runtime, agent, number, and callback path.
• Connect Bolna AI callingConnect a controlled Bolna runtime, agent, number, and callback path.

Setup route: /app/calls/settings/providers

Open setup

Social and website channels

Supported

Instagram · Samvaad website chat · Samvaad website call

Communication · 3 provider guides

DetailsClose

Prepare

An approved channel account A routing owner Webhook readiness

Connect

Open /app/instagram/settings in the correct workspace and save the connection there.

Test

Use a provider test account or website test session without customer data.

Monitor

Review provider link, webhook state, routing, identity matching, and recent failures.

Recover

Repair the provider link or routing and retest with a new test identity.

Rotate

Reconnect OAuth or rotate provider credentials before the old access is revoked.

Disconnect

Disable the website widget or provider intake before removing the Sakhaa connection.

Limits

Meta and Samvaad connection and webhook requirements apply.

Fallback

Disable new channel intake and route approved conversations to the existing inbox or manual owner.

Role and credentials

Company admin. OAuth or linked provider configuration

Provider guides

• Connect InstagramRoute supported Instagram conversations into the correct Sakhaa inbox.
• Connect Samvaad website chatRoute supported website chat sessions into Sakhaa.
• Connect Samvaad website callingRoute supported website call requests into the controlled calling path.

Setup route: /app/instagram/settings

Open setup

API clients

Supported

Sakhaa Capture API

Developer · 1 provider guide

DetailsClose

Prepare

A server-side secret store A dedicated client for each integration

Connect

Open /app/api-clients in the correct workspace and save the connection there.

Test

Call the API information endpoint, then capture one synthetic person with an idempotency key.

Monitor

Review client status, rate limit, request statistics, failures, and mappings.

Recover

Correct the request or client settings. Use the same idempotency key only for the same logical request.

Rotate

Regenerate the secret, update the server-side integration, then remove the old secret.

Disconnect

Deactivate the client before deletion and confirm the replacement intake path.

Limits

Each client has its own rate limit, source mapping, and active state.

Fallback

Keep the existing client or a reviewed manual intake path active until the replacement client passes a synthetic request.

Role and credentials

Company admin. X-API-Key and one-time X-API-Secret

Provider guides

• Connect a Capture API clientCreate one server-side client and capture a synthetic person exactly once.

Setup route: /app/api-clients

Open setup

Use synthetic data or an approved test identity. Provider approval, quotas, billing, and tenant activation remain separate from documentation proof.