Apollo integrations

Apollo integrations, and the six-hour window

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.

apollo.io 7 integrations
layerData, Prospecting, Engagement
entry$49/user/mo
authAPI key in the x-api-key header
automationSync settings with field mapping...
verified2026-09-18
checked Guides written 7 of 7
7integrations checked
6built natively
3sync both ways
4need a plan upgrade
The short version

What decides a Apollo integration

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.

All 7

Every Apollo 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 7 of 7
↔

Apollo and HubSpot

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
←

Apollo and Clay

One way, in
BuiltNative

A native provider column, and the cheapest first step in most waterfalls.

  • Moves: Contacts, Companies
  • Needs: Any Clay plan, plus your own Apollo account. Clay's catalogue marks every Apollo action as needing one.
Metered by usage · minutes Read the guide
↔

Apollo and Slack

Two-way sync
BuiltNativeMarketplace appBuilt on the API
WatchNo upgrade needed

Not an alert feed any more: you prospect, enrich and sequence by typing in Slack.

  • Moves: Messages, Activities, Contacts
  • Needs: An Apollo plan and a Slack workspace. An Apollo admin to connect it, and professional or organization for agents.
Included on both sides · minutes Read the guide
←

Apollo and LinkedIn

One way, in
BuiltNative

Not an integration. A browser extension, against a user agreement that forbids one.

  • Moves: Contacts, Companies
  • Needs: A paid Apollo plan for the CRM hop, credits for each save, and a reading of LinkedIn's terms
Metered by usage · minutes 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
→

Apollo and Outreach

One way, out
BuiltNative
WatchPaid licence first

One Outreach account per Apollo workspace, so connect an admin or nobody sees the sequences.

  • Moves: Contacts, Lists
  • Needs: An Outreach contract, a paid Apollo plan, and an admin Outreach account to connect
Paid add-on or licence · minutes Read the guide
Buyer's guide

How to pick, and what to check first

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

01

Decide what Apollo may create before you map anything

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.

02

Do not enable it on a Friday

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.

03

Use the list direction, because most teams forget it

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.

04

Activity logging is the reason, usually

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.

Written up

The Apollo 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 Apollo 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

Apollo integrations, asked and answered

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

Does Apollo's free plan include CRM integrations?

No. CRM integrations are excluded from the free tier. Basic, at $49 per user per month on annual billing, is where they start.

What is the six-hour window?

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.

Does Apollo sync both ways?

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.

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 7 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