CRM

The CRM layer, and what has to reach it

Every other layer in a sales stack is ultimately judged on what it can write into this one.

crm 6 tools
layerCRM
forThe system of record
tools here6
integrations33
with a guide33
checked Tool hubs 3 of 6
The short version

What this layer is actually for

The system of record. In this directory that is HubSpot, Salesforce, Attio, Pipedrive, Zoho and monday.

The CRM is the only layer whose job is to still be correct in two years. Everything else is a pipeline that moves records towards it, which is why an integration is nearly always evaluated on what it writes here rather than on what it reads.

That makes two questions decide most CRM integrations, and both are answered on the record pages rather than asserted here: whether the sync runs both ways, and whether the vendor gates it behind a tier you do not currently buy. A read-only integration and a two-way one are the same feature with completely different consequences for the system of record.

In this layer

The 6 tools this directory covers in the CRM layer

A tool can sit in more than one layer, and several here do. The layers on each card are the full set, not just this one.

The data layer

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

Start for free
Showing 6 of 6

Salesforce

The CRM everything integrates with, eventually
12 integrations
LayerCRM
Guides +4

Almost every tool here ships a Salesforce connector, because enterprise buyers demand one. What varies wildly is whether your edition can use it: API access itself is an edition feature, and several integrations that look standard quietly require Enterprise.

  • API access is an edition feature, not a universal one
  • Group Edition is not supported by the HubSpot connector at all
  • Selective sync between HubSpot and Salesforce needs a Salesforce Enterprise licence
Entry priceQuote only Visit See the 12 integrations

Attio

The CRM whose objects you define
3 integrations
LayerCRM
Guides

Attio matters to an integration directory for one reason: the objects are yours. If your motion runs on something that is not a contact and a deal, every other integration on this site is a mapping exercise and Attio's is a schema decision.

  • Objects and attributes defined through the API, not just in the interface
  • Ships an official MCP server alongside the REST API
  • Thinner native integration list than HubSpot or Salesforce
Entry price$0/mo Visit See the 3 integrations

Pipedrive

A pipeline a sales team will actually keep up to date
LayerCRM
Guides

Pipedrive is the CRM teams choose when they want the deal board and not the platform, which makes its integration story unusually legible: there is a well documented REST API, there are webhooks on every plan, and there is an automation builder that can fire one outward. What it cannot do is read the answer back, and that single gap shapes every enrichment design on it.

  • Webhooks on every plan, and a webhook action inside automations from Growth
  • A daily API budget in tokens rather than a flat call count
  • The automation webhook is global admin only, and cannot use the response
Entry price€14/seat/mo Visit On the Reverse Contact hub

Zoho CRM

A CRM bought as part of a whole software estate
LayerCRM
Guides

Zoho CRM is the only CRM in this directory that ships its own programming language. Deluge runs inside the product, calls external APIs with invokeUrl, and turns an enrichment build into a function rather than a pipeline. The catch is the edition: functions are fully available on Enterprise and above, and Standard and Professional reach them only through extensions.

  • Deluge functions call external APIs directly from a workflow rule
  • Functions in full only on Enterprise, CRM Plus, Ultimate and Zoho One
  • API limits are credits in a 24-hour window, not calls per minute

monday CRM

A sales team already living in the same boards as everyone else
LayerCRM
Guides

monday CRM is boards rather than objects, which makes it pleasant to change and awkward to enrich: there is no contact schema to map into, only columns somebody named. The API is GraphQL with a complexity budget, and the limit that decides an enrichment build is not the complexity but the daily call count, which is 1,000 until you reach Pro.

  • GraphQL API with a complexity budget and a separate daily call limit
  • 1,000 API calls a day on Basic and Standard, 10,000 on Pro
  • Custom automations start at Standard, 250 a month
Entry price€12/seat/mo Visit On the Reverse Contact hub

What a CRM integration is really being asked is whether it can write without making the record worse. A field-level mapping you control and a fixed mapping you do not are the difference between enrichment and overwriting.

Across the edge

33 integrations that touch this layer

Each record carries the layers it spans, so an integration appears here when this layer is one of them. Start with how it is built, because a native app and a webhook you maintain are the same feature with completely different owners.

33 of these 33 have a full guide behind them, HubSpot and LinkedIn and HubSpot and ZoomInfo among them. All 8 worked stacks here run on this layer, among them Inbound speed to lead and The CRM data layer.

The data layer

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

Start for free
Showing 33 of 33
↔

HubSpot and ClickUp

Two-way sync
BuiltNativeMarketplace appZapier, Make or n8n
WatchNeeds a higher plan

The rare pair where each vendor built the half that runs inside the other.

  • Moves: Deals, Contacts, Companies, Tasks
  • Needs: HubSpot workflows for the automated direction, so Professional or above
Needs a higher plan · minutes Read the guide
↔

HubSpot and Clay

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

Read a filtered slice, fill the gaps, write it back, on a schedule. From Clay Growth up.

  • Moves: Contacts, Companies, Deals, Lists
  • Needs: Clay Growth or above, where CRM integrations start. Nothing extra on HubSpot.
Needs a higher plan · hours Read the guide
⋅

HubSpot and Slack

Events only
BuiltNativeMarketplace app
WatchNeeds a higher plan

Notifications are easy. Routing to the right channel is the part nobody built.

  • Moves: Activities, Messages, Deals, Companies
  • Needs: HubSpot Professional or Enterprise to create a channel from a workflow
Needs a higher plan · minutes Read the guide
↔

HubSpot and Salesforce

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
↔

HubSpot and Apollo

Two-way sync
BuiltNativeMarketplace app
WatchNeeds a higher plan

Records both ways, sequence activity logged, and a six-hour window you should not miss.

  • Moves: Contacts, Companies, Deals, Activities, Lists
  • Needs: Apollo Basic or above. The free plan excludes CRM integrations.
Needs a higher plan · hours Read the guide
↔

HubSpot and Make

Two-way sync
BuiltZapier, Make or n8n
WatchNo app, you build it

A Super Admin has to approve it, and a scope added to a connection can never be removed.

  • Moves: Contacts, Companies, Deals, Custom objects
  • Needs: A HubSpot Super Admin to approve the app, and a developer account for webhook modules
Metered by usage · hours Read the guide
↔

HubSpot and Outreach

Two-way sync
BuiltNativeMarketplace app
WatchPaid licence first

Contacts both ways, email one way, and HubSpot rather than Outreach owns it.

  • Moves: Contacts, Activities
  • Needs: An Outreach contract, and Super Admin or App Marketplace permissions in HubSpot. Custom field mappings need Data Hub.
Paid add-on or licence · hours Read the guide
↔

HubSpot and Gong

Two-way sync
BuiltNativeMarketplace app
WatchPaid licence first

Six hours before a call appears, and the transcript never does.

  • Moves: Activities, Deals, Contacts, Companies
  • Needs: A Gong contract, a HubSpot tech admin, and a dedicated integration user
Paid add-on or licence · hours Read the guide
←

HubSpot and Smartlead

One way, in
BuiltNativeBuilt on the API

The campaign-level sync is creation-time only. SmartAgents is the way around it.

  • Moves: Contacts, Activities
  • Needs: A Smartlead plan and a HubSpot account that can authorise OAuth. A campaign not yet live for the native sync, or SmartAgents access for the other route.
Metered by usage · hours Read the guide
↔

HubSpot and lemlist

Two-way sync
BuiltNativeMarketplace app
WatchNo upgrade needed

Opens and clicks arrive as notes, because HubSpot will not let a third party write them.

  • Moves: Contacts, Companies, Activities
  • Needs: A paid lemlist plan (there is no free tier), plus admin access on both sides
Included on both sides · hours Read the guide
→

HubSpot and Attio

One way, out
BuiltNativeBuilt on the API
WatchNeeds a higher plan

Not an integration. A one-time migration, and it will not update what it finds.

  • Moves: Contacts, Companies, Deals
  • Needs: Attio Plus, Pro or Enterprise, a workspace admin, and a decision to leave HubSpot
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
↔

Clay and Attio

Two-way sync
BuiltNative
WatchNeeds a higher plan

Write to objects you defined yourself, rather than to contacts and deals.

  • Moves: Contacts, Companies, Custom objects
  • Needs: Clay Growth or above, an Attio workspace, and an Attio workspace admin to authorise the connection
Needs a higher plan · hours Read the guide
↔

Apollo and Salesforce

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
The data layer

Where Reverse Contact sits under this layer

Reverse Contact is not a CRM tool and has no marketplace app in this layer. It is the data layer underneath it: one API that resolves an email, a domain or a profile URL into a verified people and company record, so that what this layer moves is worth moving. This directory documents 6 routes into this layer, 6 of them with a full guide.

Every documented route into a stack sits on the Reverse Contact hub.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every number on this page is derived from those records rather than typed, and each record 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-10-28
Sources
2 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