No AppExchange listing, and the callout limits are the real design constraint.
- Moves: Contacts, Companies
- Needs: A Reverse Contact API key and a Salesforce edition with API access
Twelve integrations, and a pattern that repeats on almost all of them: the connector is free, the edition that can run it is not, and API access is itself an edition feature.
The widest integration surface, gated by edition.
Almost every tool in this directory ships a Salesforce connector, because enterprise buyers demand one. That makes the interesting question not whether an integration exists but whether your org can use it, and the answer usually turns on three things: the edition, the API allocation and the admin queue. The Salesforce data layer works all three through on one build, in the order they bite.
API access is the first gate and the one people forget. Editions without it cannot run most of what is on this page regardless of what you hold on the other side. HubSpot's connector documents the point sharply: it needs a Salesforce edition with API access, selective sync needs a Salesforce Enterprise licence, and Group Edition is not supported at all.
The second gate is human. Installing most of these needs Modify Metadata, Download AppExchange Packages and Customize Application, which means a Salesforce admin, a sandbox and a change window. That is why integrations that take an afternoon on HubSpot take a fortnight here, and none of it is technical difficulty.
Salesforce sits in the CRM layer, with 5 other tools in this directory. Counted across the whole directory it reaches 12 of the other 22 tools, and the integration matrix shows that row against every other.
Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.
Whichever of these you connect, the integration moves the record. We fill it.
Start for freeNo AppExchange listing, and the callout limits are the real design constraint.
Two CRMs, one connector, and an edition requirement on both sides.
The original CRM Sync target, with the same Advanced Plus gate.
The same read, enrich, write loop, against an org with stricter rules.
The one pair where the same company owns both sides.
Enrichment on creation and on a schedule, and a sandbox that charges you to test.
Per-object, per-field control in both directions, and Essentials cannot run it at all.
Take a field off the integration user and Gong deletes what it already imported.
Five access tokens per org, and the sixth app silently revokes the first.
Two integrations, both on Business Plus, and only the names sync both ways.
Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.
Six hours to configure it, then it turns itself on whether or not you finished.
4 things that decide whether a Salesforce integration will work for you, in the order they usually bite.
API access is an edition feature. So is selective sync on the HubSpot connector, which needs Salesforce Enterprise. Confirm what your licence actually carries before evaluating anything, because no amount of configuration moves a feature down an edition.
Salesforce meters daily API requests by edition and licence count, across every integration in the org. A new enrichment loop writing row by row is competing with your existing connectors for the same allocation, and the symptom of running out is other people's integrations failing.
Required fields, validation rules, duplicate rules and Apex triggers all still apply to anything writing in. A tool reporting a successful run is reporting that it sent the request. Test the write path in a sandbox and read the errors before you scale it.
Modify Metadata, Download AppExchange Packages and Customize Application are not permissions a RevOps lead usually holds. The install is short and the queue in front of it is not, which is the real timeline on every project on this page.
Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.
No AppExchange listing, and the callout limits are the real design constraint.
One way, in → 02Two CRMs, one connector, and an edition requirement on both sides.
Two-way sync → 03The original CRM Sync target, with the same Advanced Plus gate.
Two-way sync → 04The same read, enrich, write loop, against an org with stricter rules.
Two-way sync → 05The one pair where the same company owns both sides.
Events only → 06Enrichment on creation and on a schedule, and a sandbox that charges you to test.
One way, in → 07Per-object, per-field control in both directions, and Essentials cannot run it at all.
Two-way sync → 08Take a field off the integration user and Gong deletes what it already imported.
Two-way sync → 09Five access tokens per org, and the sixth app silently revokes the first.
Two-way sync → 10Two integrations, both on Business Plus, and only the names sync both ways.
Two-way sync → 11Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.
Two-way sync → 12Six hours to configure it, then it turns itself on whether or not you finished.
Two-way sync →The hub most sales stacks are actually built around.
See the 17 integrations →A CRM with a data model you write yourself.
See the 3 integrations →People and company data for every tool in this directory.
See the 22 integrations →Deep native CRM integrations, sold by tier.
See the 3 integrations →One integration that carries data, sequences and activities.
See the 7 integrations →An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.
Free trial, no card required, and 500 credits to start.
The questions that come up before anyone opens a setup guide.
Because API access is sold as an edition feature rather than included universally. Any integration that reads or writes records needs it, so an edition without API access rules out most of this page. HubSpot's connector adds two further conditions: selective sync requires Salesforce Enterprise, and Group Edition is not supported at all.
Yes, through Flow with an API callout, through n8n or Make, or through a Clay table that reads and writes Salesforce records. Reverse Contact is the example in this directory: no AppExchange listing, and three working routes.
Days rather than hours, and almost none of that is the integration. The slow parts are the admin permissions, the sandbox test and the change window. Plan around the admin's queue rather than around the setup guide.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.