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.
More integrations point at HubSpot than at any other tool in this directory, which is the real reason teams pick it and the real reason they struggle to leave. The catch is that the automation that makes those integrations useful sits behind Professional, so the marketplace listing and the working integration are two different purchases.
Workflows, the thing most integrations trigger from, start at Professional
A private app you build gets 190 requests per 10 seconds; a marketplace app gets 110
Free CRM API access on every tier, including the free one
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
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
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
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
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
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.
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.
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.
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 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.
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.