Two providers, no integration. Apollo cannot tell you what a waterfall call will cost, and says so.
- Moves: Contacts, Companies
- Needs: An Apollo paid plan for API enrichment, a Reverse Contact API key, and an orchestrator to run the waterfall
Seven integrations. Six of them run on one connector that moves more than most, and the seventh is not an integration at all but a waterfall against a competitor.
One integration that carries data, sequences and activities.
Apollo sells data and sending in one product, so its CRM integration has to carry more than a typical connector. Contacts, accounts and deals move in both directions, sequence activity logs to the CRM timeline as calls, emails, meetings, tasks and notes, and CRM lists travel the other way to drive targeting. That breadth is the argument for it and the reason the sync settings deserve real attention.
The operational detail worth knowing before anything else: on a paid plan, enabling the integration starts a six-hour window to configure sync settings and map fields, after which syncing enables itself with whatever configuration exists. Read the settings first, decide what each object should do, then enable.
CRM integrations are excluded from Apollo's free plan, so Basic at $49 per user per month on annual billing is the entry point for everything on this page. API Enrichment and Waterfall Enrichment are listed on the same plan, which is why the one page here that is not a connector starts at the same price.
That page is the exception to everything above. Reverse Contact is a competing data provider rather than a tool Apollo connects to, so there is no sync, no six-hour window and no field mapping, and what people build instead is a waterfall orchestrated somewhere else. It is on this hub because the comparison is the thing buyers actually want, and because Apollo turns out to be a waterfall orchestrator itself: its own documentation describes a configurable list of data sources and says it cannot state what a miss costs, since that depends on which sources your admin chose.
Apollo sits in 3 of the seven layers this directory splits a stack into, the data layer and the prospecting layer among them, which is why it turns up in so many pairs. Counted across the whole directory it reaches 7 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 freeTwo providers, no integration. Apollo cannot tell you what a waterfall call will cost, and says so.
Records both ways, sequence activity logged, and a six-hour window you should not miss.
A native provider column, and the cheapest first step in most waterfalls.
Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.
Not an integration. A browser extension, against a user agreement that forbids one.
Six hours to configure it, then it turns itself on whether or not you finished.
One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences.
4 things that decide whether a Apollo integration will work for you, in the order they usually bite.
A two-way sync between a prospecting database and your system of record means the prospecting database can create records. Without a rule for what qualifies, the CRM fills with people nobody chose to contact and your reporting stops meaning anything.
The six-hour configuration window runs whether or not anyone is watching. Enable at the start of a working day, with the settings decided in advance.
CRM lists feeding Apollo is the underrated half of this connector. Segmentation logic that took months to get right already lives in the CRM, and pushing it across beats rebuilding the same filters in a second tool.
Most teams set this up for sequence activity on the CRM timeline. If that is your reason, confirm which activity types map to which CRM objects before you judge whether it worked.
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.
Two providers, no integration. Apollo cannot tell you what a waterfall call will cost, and says so.
One way, out → 02Records both ways, sequence activity logged, and a six-hour window you should not miss.
Two-way sync → 03A native provider column, and the cheapest first step in most waterfalls.
One way, in → 04Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.
Two-way sync → 05Not an integration. A browser extension, against a user agreement that forbids one.
One way, in → 06Six hours to configure it, then it turns itself on whether or not you finished.
Two-way sync → 07One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences.
One way, out →The hub most sales stacks are actually built around.
See the 17 integrations →The widest integration surface, gated by edition.
See the 12 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 →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.
No. CRM integrations are excluded from the free tier. Basic, at $49 per user per month on annual billing, is where they start.
After enabling the HubSpot integration on a paid plan, there is a six-hour period in which to configure sync settings and map fields. At the end of it, syncing is automatically enabled with whatever configuration is in place. It is not a trial and waiting does not cancel it.
Yes. Contacts, accounts and deals move in both directions, activity pushes from Apollo to the CRM, and CRM lists pull into Apollo. Whether you want all of that on is a separate question, and the sync settings are where you answer it.
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.