Skip to content

Integrations Overview

The Integrations hub is where you connect SIPSTACK to the other tools your team already uses. Browse a Marketplace of CRM, helpdesk, collaboration, and automation connectors, connect the ones you need, and manage every live connection from one place. Open it from the sidebar: Account → Integrations (/account/integrations).

Watch on YouTube ↗

Integrations Marketplace in dark mode

The hub has four tabs:

TabWhat it does
MarketplaceBrowse the full connector catalog, grouped by category, and connect a provider.
ConnectionsManage the connections you’ve already made — view status and disconnect.
WebhooksRegister outbound webhook endpoints, pick their events, view the delivery log, and send a test event.
API keysCreate and manage API keys — name, scopes, and expiry — plus usage, revoke, and regenerate.

The Marketplace lists every connector grouped by category — CRM, Helpdesk & Support, Collaboration & Productivity, and Automation. Use the product filter chips (All / Nova / Flare / Aura) at the top to narrow the catalog to connectors built for a specific product.

Each card shows:

  • The connector name and a one-line description of what it does.
  • A status pill — Available (connect now), Beta (early access), or Coming soon (on the roadmap).
  • Product badges (Nova / Flare / Aura) for the products the connector works with.
  • A Connect button for connectors that support one-click OAuth. Once connected, the card flips to a Connected pill with a Disconnect action.

For what each connector does once it’s connected, see the Connector Reference.

Connectors for a product you’re not subscribed to render locked (never hidden) with an upgrade link, so you can always see what’s possible on a higher plan.

Connecting a CRM is included on Nova Ultra and above. On lower tiers, CRM cards show an Included on Nova Ultra badge with an upgrade link instead of a Connect button — see Subscriptions to change your plan. Browsing the Marketplace itself is open to any organization member; the connect/disconnect actions require the integrations.manage permission (see Permission Groups).


For a one-click OAuth connector (for example, a CRM):

  1. Open Account → Integrations and stay on the Marketplace tab.
  2. Find the connector and click Connect. A consent sheet summarizes exactly what SIPSTACK will be allowed to do (the scopes it requests).
  3. Confirm to be redirected to the provider’s authorization screen, sign in, and approve access.
  4. You’re returned to SIPSTACK and land on the Connections tab with the new connection listed.

SIPSTACK stores only an encrypted, write-only token for the connection — your credentials are never readable back out of the app.

Salesforce: install the SIPSTACK package first

Section titled “Salesforce: install the SIPSTACK package first”

Salesforce needs one extra step from your Salesforce admin before you click Connect. SIPSTACK for Salesforce ships as a managed package that adds the SIPSTACK app and the SMS consent fields to your org.

  1. Install the package. Your Salesforce admin opens the SIPSTACK for Salesforce install link (for a sandbox, use this link instead), signs in and chooses Install for Admins Only.
  2. Assign the permission set. In Salesforce Setup → Permission Sets → SIPSTACK Integration → Manage Assignments, add the user who will connect SIPSTACK. This lets that user read and update the SIPSTACK fields.
  3. Allow the app. In Setup → External Client App Manager → SIPSTACK → Edit Policies, set Permitted Users to All users may self-authorize and IP Relaxation to Relax IP restrictions, then save.
  4. Connect. Back in SIPSTACK, click Connect on the Salesforce card, pick Production or Sandbox, and sign in as the user from step 2.

The package adds these fields to both Contact and Lead. Their API names carry the package’s sipstack__ prefix, for example sipstack__SIPSTACK_SMS_Opted_Out__c:

FieldAPI name
SIPSTACK SMS opted outsipstack__SIPSTACK_SMS_Opted_Out__c
SIPSTACK SMS opted out atsipstack__SIPSTACK_SMS_Opted_Out_At__c
SIPSTACK SMS opt-out sourcesipstack__SIPSTACK_SMS_Opt_Out_Source__c
SIPSTACK SMS consent statussipstack__SIPSTACK_SMS_Consent_Status__c
SIPSTACK SMS consent basissipstack__SIPSTACK_SMS_Consent_Basis__c
SIPSTACK SMS consent datesipstack__SIPSTACK_SMS_Consent_Date__c
SIPSTACK SMS consent evidencesipstack__SIPSTACK_SMS_Consent_Evidence__c
SIPSTACK last synced atsipstack__SIPSTACK_Last_Synced_At__c

SIPSTACK never creates or changes fields in your org itself; they come only from the package.

If the Salesforce connection card shows “SIPSTACK for Salesforce isn’t installed, or your user hasn’t been given the SIPSTACK Integration permission set. Ask your Salesforce admin.”, the package is missing or the connected user doesn’t have the permission set. Fix either one and the card clears by itself within a few minutes; you don’t need to reconnect.


The Connections tab lists every live connection for your organization: the provider, the connected account, its status, and when it was connected. Disconnect any one of them with the Disconnect action (revokes the stored token and stops syncing — you can reconnect at any time from the Marketplace).

Integrations Connections tab showing connected CRMs

Below your provider connections, the Agent tool credentials section lists the named external APIs (base URL + auth header) that your Aura voice agents can call from a flow. These are distinct from the OAuth connections above — see Connections for the full guide on adding and testing them.


Beyond the hub — webhooks and the REST API

Section titled “Beyond the hub — webhooks and the REST API”

The Marketplace covers managed, one-click connectors. For everything else, SIPSTACK exposes two lower-level building blocks:

  • Webhooks — SIPSTACK pushes real-time, HMAC-signed HTTP POSTs to your endpoint when events happen — message delivery, inbound SMS, live call lifecycle (ringing / answered / hangup for screen-pop), call completion, campaign completion, and Aura AI voice-agent call start/completion (aura.call.started / aura.call.completed), and SMS opt-out / consent changes for CRM suppression sync (contact.opted_out / contact.opted_in / contact.consent_changed, rolling out). Pairs well with no-code platforms like n8n, Make, and Zapier.
  • REST API — the same API that powers Switchboard, available for programmatic use. The API-key surface (/api/v2/...) spans all three products: send SMS/MMS (Flare), full contacts CRUD + search, click-to-call and read call history / voicemails (Nova), read AI voice-agent calls with transcripts and outcomes (Aura), search and buy numbers + register E911, and manage webhook endpoints from your own code. Number ordering (POST /api/v2/numbers/order) is available by default (operators can disable it with a kill-switch); broader provisioning write automation such as PBX configuration is coming soon — if you need it today, tell support and we’ll help you get it done. See Authentication for session tokens and API keys.

You want to…Use
Connect a CRM, helpdesk, or productivity toolAccount → Integrations → Marketplace
Let an AI voice agent act on your data during a callAura Connections
React when something happens in SIPSTACK (incl. live call screen-pop)Webhooks
Send SMS/MMS, manage contacts, pull call history, or place a click-to-call from your codeREST API
Read AI voice-agent calls with transcripts & outcomesREST API (Aura)
Buy numbers & register E911 from your codeREST API (Numbers)
Automate broader provisioning (configure PBX) from your codeComing soon — tell support
Connect to a no-code tool (n8n, Make, Zapier)Webhooks (trigger) + REST API (action)

For integration help, open a ticket from Switchboard (avatar menu → Support) or email support@sipstack.com.