Integrations an enterprise sales platform needs
Email, calendar and identity first, then documents and meetings, and how to judge each one.
The SalesOS team
8 min read
Every sales platform has an integrations page with a wall of logos, and every one of them looks the same from a distance. The logos tell you a connector exists. They do not tell you whether it moves the data you need, in the direction you need, quickly enough to matter, or what happens on the day it breaks.
If you are choosing a platform for a team of more than a few dozen people, the integrations that matter are fewer than the logo wall suggests, and they matter in a particular order. Get the first group wrong and the rest will not save you.
The logo wall problem
A connector that imports contacts once a night and a connector that keeps two systems in step within a minute are both shown as the same logo. So are a native integration the vendor maintains and a template on a third party automation service that nobody at the vendor has looked at in a year.
The question to keep asking is not “do you integrate with X?” but “what exactly happens to my data when I connect X, and how will I know if it stops?”.
Day one: email, calendar, identity
These three decide whether reps will use the system at all. If email and meetings do not land on the record by themselves, reps will be asked to log them by hand, and they will not.
You need two way sync with the mail system your company already uses, which in practice means Google Workspace or Microsoft 365, plus a fallback for anything else. Sent and received messages should attach to the right contact and deal automatically, and replies should be detected so an outreach sequence stops when the buyer answers. Check how it decides which record an email belongs to when a contact sits on three open deals.
Calendar
Meetings should appear against the deal without anyone touching them, in each person’s own time zone. A surprising number of tools still get time zones wrong, which you will discover when a rep in Singapore sees a London meeting at the wrong hour.
Identity
For an enterprise rollout this is not optional. Single sign on (SAML or OIDC, through Okta, Entra ID, Google or similar) means people sign in the way they sign in to everything else, and that switching someone off in one place switches them off everywhere. SCIM provisioning means accounts are created and removed by your identity provider rather than by an admin remembering to do it. When someone leaves, their access to your customer list should end the same afternoon.
Soon after: documents, meetings, chat
These remove the copy and paste between systems that happens around every deal.
- Signatures. Quotes and contracts should go out for signature from the deal, and the signed copy and its status should come back to it. Whether that is built in or runs through DocuSign matters less than whether the deal knows it has been signed.
- Video meetings. Zoom or Teams meetings that are recorded and transcribed are worth far more when the transcript sits on the deal, where the next person preparing for a call can read it.
- Team chat. A message in Slack or Teams when a large deal moves or a hot lead arrives. Keep this small. A channel that announces everything is muted within a week.
Later: enrichment and automation
Data enrichment (ZoomInfo, Clearbit and their competitors) fills in company size, industry and contact details. It is useful, and it is also the integration most likely to quietly overwrite something a rep typed by hand. Find out whether enrichment fills empty fields only or replaces existing values, and whether you can choose.
Automation tools such as Zapier, and the platform’s own API and webhooks, are how you connect everything that will never have a native integration: your billing system, your product database, the internal tool someone built in 2019. Here the questions are technical. Are webhooks signed so you can tell they are real? Are failed deliveries retried, or lost? Are API keys limited to what they need?
How to judge one integration
For any integration you depend on, get specific answers to these.
| Question | Why it matters |
|---|---|
| Which direction? | One way imports leave the other system out of date the moment a rep edits a record. |
| How fast? | Overnight is fine for enrichment and hopeless for a lead that should be called within five minutes. |
| Which fields? | Custom fields are where integrations most often fall short, and where your business usually lives. |
| Who wins a conflict? | If both sides change the same field, one of them is overwritten. Know which, before it happens. |
| Per user or per company? | A per user mailbox connection breaks when that person leaves; a company wide one needs admin consent. |
| How will I know it broke? | Ask to see the error view. A sync that fails silently is worse than none, because people trust it. |
| What permissions does it ask for? | A connector that wants full access to a mailbox to log sent mail deserves a second look. |
The single most revealing request in a demo is “show me what it looks like when this sync fails”. Vendors who have thought about it will show you straight away. Others will change the subject.
What SalesOS connects to
On every plan: email sync with Gmail, Outlook or any IMAP mailbox, with opens, clicks and replies tracked; and calendar sync with Google, Outlook and Apple calendars. On Professional, contracts and quotes go out for electronic signature from the deal, and Salesforce connects with live two way access. On Enterprise: single sign on (SAML and OIDC) with SCIM provisioning, the public API, signed webhooks with retries, and the integrations hub, which adds HubSpot, Slack, Microsoft Teams, Zoom, Calendly, DocuSign, ZoomInfo, Clearbit, LinkedIn and Zapier.
That is a shorter list than some platforms show. We would rather list what works than what we hope to build. The full catalogue is on the integrations page, and if you are comparing platforms more broadly, the CRM comparisons go into how we differ from the usual suspects.