Salesforce integrations

Salesforce integrations, gated by an edition, not a toggle

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.

salesforce.com 12 integrations
layerCRM
entryQuote only
authOAuth 2.0, connected app
automationFlow, on every edition with API ...
verified2026-09-18
checked Guides written 12 of 12
12integrations checked
9built natively
9sync both ways
9need a plan upgrade
The short version

What decides a Salesforce integration

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.

All 12

Every Salesforce integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 12 of 12
↔

Salesforce and HubSpot

Two-way sync
BuiltNativeMarketplace app
WatchNeeds a higher plan

Two CRMs, one connector, and an edition requirement on both sides.

  • Moves: Contacts, Companies, Deals, Activities, Custom objects
  • Needs: HubSpot Professional or Enterprise, and a Salesforce edition with API access
Needs a higher plan · days Read the guide
↔

Salesforce and Clay

Two-way sync
BuiltNativeBuilt on the API
WatchNeeds a higher plan

The same read, enrich, write loop, against an org with stricter rules.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, a Salesforce edition with API access, and a full user licence to authenticate
Needs a higher plan · hours Read the guide
⋅

Salesforce and Slack

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

The one pair where the same company owns both sides.

  • Moves: Deals, Activities, Messages, Contacts
  • Needs: Sales Cloud, plus a Slack workspace you can install apps into
Needs a higher plan · minutes Read the guide
↔

Salesforce and Gong

Two-way sync
BuiltNativeMarketplace app
WatchPaid licence first

Take a field off the integration user and Gong deletes what it already imported.

  • Moves: Activities, Deals, Contacts
  • Needs: A Gong contract, a Salesforce edition with API access, and a dedicated integration user
Paid add-on or licence · hours Read the guide
↔

Salesforce and Zapier

Two-way sync
BuiltZapier, Make or n8nMarketplace app

Five access tokens per org, and the sixth app silently revokes the first.

  • Moves: Contacts, Companies, Deals, Custom objects
  • Needs: A paid Zapier plan, a Salesforce edition with API access, and an admin to approve the app
Metered by usage · minutes Read the guide
↔

Salesforce and ClickUp

Two-way sync
BuiltNativeMarketplace app
WatchNeeds a higher plan

Two integrations, both on Business Plus, and only the names sync both ways.

  • Moves: Tasks, Deals, Companies
  • Needs: ClickUp Business Plus or Enterprise, a Salesforce admin, and beta access for the sync
Needs a higher plan · hours Read the guide
↔

Salesforce and n8n

Two-way sync
BuiltZapier, Make or n8nBuilt on the API
WatchNo app, you build it

Connected Apps are on the way out, and n8n Cloud needs a permission admins lack by default.

  • Moves: Contacts, Companies, Deals, Tasks, Custom objects
  • Needs: An n8n instance, a Salesforce edition with API access, and an External Client App
Metered by usage · hours Read the guide
↔

Salesforce and Apollo

Two-way sync
BuiltNativeMarketplace app
WatchNeeds a higher plan

Six hours to configure it, then it turns itself on whether or not you finished.

  • Moves: Contacts, Companies, Deals, Activities
  • Needs: Apollo Basic or above, a Salesforce edition with API access, and a Salesforce admin
Needs a higher plan · hours Read the guide
Buyer's guide

How to pick, and what to check first

4 things that decide whether a Salesforce integration will work for you, in the order they usually bite.

01

Check the edition before the feature list

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.

02

The API allocation is shared and finite

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.

03

Validation rules will reject writes, correctly

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.

04

Budget for the admin, not the app

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.

Written up

The Salesforce integrations with a full guide

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.

Other tools

Integrations for the rest of the stack

Connecting Salesforce is half the job

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.

FAQ

Salesforce integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Why does an integration need a specific Salesforce edition?

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.

Can I connect a tool with no AppExchange listing?

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.

How long does a Salesforce integration take to set up?

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.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 12 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

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.

Ask an assistant