This page lists the connectors you can turn on from Account → Integrations → Marketplace and what each one does once it’s connected. For how to browse, connect and disconnect, see the Integrations Overview.
A few things hold for every connector:
- Screen-pop means that when a call rings, SIPSTACK looks the caller’s number up in the connected system and shows the matching person or record. The lookup happens live on each call, so it reflects the system’s current data.
- Call logging writes completed (and, where noted, missed) calls back into the connected system. It follows the same call-logging setting as your other CRM connections.
- Automated texts are off until you turn them on. Every connector that can send SMS (order confirmations, reminders, follow-ups) starts with each automation switched off. You enable it and pick the sending number in that connector’s settings. You’re responsible for having permission to text the people you message. Turning on an automation is not legal advice, and it doesn’t make a campaign compliant with the TCPA, CASL or any other law.
- Actions are lookups that an Aura voice agent or the REST API can run during a call (for example “what’s the status of my order?”). When an action runs from an agent or an API key, the caller’s own phone number is the key. A caller can only get back records tied to the number they’re calling from.
- Credentials are stored encrypted and can’t be read back out of SIPSTACK. A connector only ever calls its own vendor’s servers. For connectors where you enter your tenant address (SAP, Oracle, Genesys, ServiceNow, Freshdesk), SIPSTACK accepts only that vendor’s own domains.
Availability depends on your plan. Each Marketplace card shows whether you can connect it on your current subscription.
| Connects with | Connectors |
|---|
| One-click sign-in (OAuth) — you approve access on the vendor’s site | Zendesk, Shopify, Stripe, Google Workspace, Pipedrive, Microsoft Dynamics 365, Clio, Jobber, Jira Service Management, QuickBooks Online |
| Credentials you enter — an API key, an integration user, or an OAuth client you create in your own account | Freshdesk, ServiceNow, SAP Sales Cloud, Oracle CX Sales, Genesys Cloud, OneRoster (school SIS), Mews, FHIR R4 (EMR) |
| A Teams webhook URL | Microsoft Teams (notifications) |
| Connector | What it does |
|---|
| Microsoft Dynamics 365 | Screen-pop from a Contact, then a Lead, that has the caller’s number. Logs each completed call as a Phone Call activity on the matched record. |
| Pipedrive | Screen-pop from the matched person, with their open-deal count. Logs calls as activities linked to the person’s most recent open deal, and adds inbound texts as notes. Stage texts: when a deal moves into a pipeline stage you’ve mapped to a message template, the deal’s contact gets that text. |
| SAP Sales Cloud (Cloud for Customer) | Screen-pop from a Contact or Individual Customer. Logs completed calls as Phone Call activities. You connect it with a technical user on your own my…crm.ondemand.com tenant. |
| Oracle CX Sales (Fusion Cloud) | Screen-pop from a Contact, along with their account. Logs completed calls as Call activities. You connect it with an integration user on your Fusion pod (….fa.….oraclecloud.com). |
| Genesys Cloud | Screen-pop from a Genesys External Contact, along with their organization. Adds a note to the contact for each completed or missed call. You connect it with an OAuth client you create in your Genesys org, plus your Genesys region. |
| Connector | What it does |
|---|
| Zendesk | Inbound texts go onto the texter’s open SMS ticket, or open a new one. Missed calls open a ticket. Optionally adds a note to the caller’s open ticket after a completed call. Screen-pop from the matched end user. Action: ticket status. |
| Freshdesk | Inbound texts and missed calls open tickets (or add to the texter’s open SMS ticket). Voicemail transcripts are attached as a private note. Screen-pop from the matched contact. You connect it with your Freshdesk domain and an agent API key. |
| ServiceNow | Inbound completed and missed calls open an Incident, with the caller set when their number matches a ServiceNow user. Screen-pop from the matched user. Action: incident status. You connect it with an integration user on your instance. |
| Jira Service Management | Inbound calls (and, optionally, inbound texts) create an issue in the project and issue type you choose. Action: issue status (from Switchboard only). Jira users have no phone field, so this connector has no screen-pop. |
| Connector | What it does |
|---|
| Shopify | Screen-pop from the matched customer. Action: order status, including tracking. Automated texts (each off until enabled): order confirmation, shipping update with tracking link, and abandoned-cart recovery. Cart recovery texts go only to buyers who ticked Shopify’s SMS-marketing consent at checkout, and only once per checkout. |
| Stripe | Connects your Stripe account (read-only). This is separate from how SIPSTACK bills you. Screen-pop from the matched customer. Actions: customer lookup and payment status. Automated texts (each off until enabled): payment confirmation, invoice reminder, failed-payment reminder and upcoming renewal. |
| QuickBooks Online | Screen-pop from the matched customer, with their open balance. Action: balance lookup, which returns the caller’s balance and open invoices. |
| Connector | What it does |
|---|
| Clio (legal) | Screen-pop from the matched contact. Billable call time: when the caller has exactly one open matter, a completed call becomes a time entry on that matter. With several open matters, the call is logged on the contact for your team to assign. Action: matter status. Appointment reminders (off until enabled) text contact attendees 24 hours before a calendar entry. |
| Jobber (field service) | Screen-pop from the matched client, and a note on the client for each call. Automated texts (each off until enabled): visit scheduled or changed, and a follow-up on quotes that have waited without a response (3 days by default). |
| OneRoster (school SIS) | Works with any student information system that offers the 1EdTech OneRoster REST API, such as PowerSchool, Infinite Campus, Skyward, Aeries or ClassLink. Screen-pop names the parent or guardian calling and their students, with grade. Action: students for this caller. Read-only. You connect it with your district’s OneRoster URL and an OAuth 2.0 client. |
| Mews (hotel PMS) | Screen-pop shows an in-house (checked-in) guest’s name and room number. Guests who aren’t checked in aren’t recognized. You connect it with the property’s Mews access token. |
| FHIR R4 (EMR / EHR) | Works with EHRs that offer a FHIR R4 API, such as Epic, Oracle Health (Cerner) and athenahealth. Screen-pop shows the patient’s name only. No clinical data is read. A number shared by several patients (a family phone) shows nothing. Optional call logging is off by default. You connect it with your FHIR base URL and a SMART backend-services client. |
| Connector | What it does |
|---|
| Google Workspace | Caller ID from the connecting user’s Google Contacts and your Workspace directory. Calendar-aware routing (optional): turns Do Not Disturb on for a Nova user while their Google Calendar shows a meeting, then turns it off when the meeting ends. It never changes a Do Not Disturb the user set themselves. Gmail SMS threads (optional): texts to a number you choose are emailed to a Workspace mailbox, one thread per texter. Replying from Gmail texts the reply back from the same number. Actions: calendar busy, contact lookup. |
| Microsoft Teams | Posts missed calls, voicemail transcripts and queue wait-time alerts to Teams channels, with a choice of events per channel. Set it up at Account → Integrations → Microsoft Teams with a webhook URL from a Teams Workflows flow (“When a Teams webhook request is received”) or a classic Incoming Webhook. Only Microsoft webhook addresses are accepted. Notifications only: this doesn’t make Nova a carrier for Teams Phone (no Direct Routing). |
