CRM Integrations for SaaS: How to Choose What to Support

Choosing which CRMs to support, how deep to go, and how to handle the ways CRMs differ.

3 min read

On this page

For many B2B products, a CRM integration is among the first that customers ask for. Sales and customer data lives in the CRM, and teams want your product to read from it, write to it, or both.

The hard part isn't building one CRM integration. It's choosing which CRMs to support, deciding how deep to go, and handling the ways CRMs differ.

Which CRMs do your customers use?#

Market share reports are less useful than your own data. Look at:

CRMs mentioned in sales calls and lost deals.
CRMs named in support requests.
CRMs used by your largest and fastest-growing customers.
CRMs common in your target segment. Small businesses, mid-market and enterprise often use different tools.

A short list of the CRMs your customers actually use is a better starting point than a long list of popular ones.

Define what the integration does#

CRM integrations usually fall into a few patterns:

Pattern	Example
Read reference data	Show a contact's CRM details inside your product
Log activity	Record that a customer opened a report or attended a meeting
Create records	Create a lead when someone signs up in your product
Two-way sync	Keep contacts or deals consistent in both systems
React to changes	Start a process when a deal changes stage

Pick one pattern for the first version. Two-way sync is the most requested and the most difficult.

How CRMs differ#

Even for "the same" data, CRMs vary:

Objects: contacts, leads, people, persons. Some separate leads from contacts; some don't.
Relationships: how contacts relate to companies and deals, and whether one contact can belong to several companies.
Pipelines and stages: configured per customer, often with multiple pipelines.
Custom fields and objects: common in CRMs, and often where customers' most important data lives.
Ownership and permissions: records may be visible only to certain users, and API access may reflect the connecting user's permissions.
API limits: rate limits and daily quotas vary, sometimes by plan.
Change notifications: webhook support and event coverage differ.

Design decisions#

Whose account connects?#

A single admin connection gives broad access but depends on one person. Per-user connections respect individual permissions but need more setup. Decide based on what data you need and how customers' teams work.

Field mapping#

Let customers map your fields to their CRM fields, including custom fields, when your use case needs it. Provide sensible defaults so setup isn't a chore.

Duplicates#

Decide how to match records: by email, by external ID, or both. Creating duplicate contacts in a customer's CRM is one of the fastest ways to lose their trust.

Conflict handling#

For two-way sync, decide which system wins when both change, and whether some fields are owned by one side.

Each customer's CRM connection is separate, with its own permissions, fields and pipelines.

Launch sequence#

Build the most requested CRM with one pattern.
Release to a few customers and watch real usage and errors.
Add mapping options and the next pattern based on feedback.
Add the next CRM, reusing your internal model where it fits.

Where Pathfix fits#

Most CRMs use OAuth for API access. Pathfix OAuth handles the authorization flow, token storage, refresh and authenticated API passthrough across 350+ providers, and supports many CRMs. Check the integrations directory for the current list. You use your own OAuth apps and call each CRM's own API, so you can work with custom fields and objects directly rather than through a normalized model.

For CRM workflows that run per customer, such as reacting to a deal stage change, Pathfix Automation can run API workflows in each connected user's context.

Frequently asked questions#

Should we use a unified CRM API?#

It can speed up coverage for standard reads. Check whether it supports the custom fields, objects and write operations your customers need.

How do we handle CRMs with strict rate limits?#

Queue work, batch requests where the API allows, back off on 429 responses, and avoid full re-syncs when incremental fetches are available.

Do we need app marketplace listings?#

Some CRMs encourage or require marketplace listing for public apps. Listings can also bring discovery. Check each CRM's developer requirements.