Records both ways, sequence activity logged, and a six-hour window you should not miss.
Apollo Basic or above. The free plan excludes CRM integrations.
Contacts, Companies, Deals, Activities, Lists, two-way sync.
The broadest single connector in this directory: contacts, accounts and deals moving both ways, sequence activity landing on the HubSpot timeline, and HubSpot lists feeding Apollo for targeting. The thing to know before you switch it on is the configuration window. After you enable the integration on a paid plan there is a six-hour period to set sync settings and map fields, after which syncing enables itself. Turn it on at the start of a working day.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Contacts and accounts | Both ways | Push from Apollo into HubSpot with mapped fields, and pull HubSpot records into Apollo. |
| Deals | Both ways | Opportunity data moves both ways, so Apollo can target on pipeline state. |
| Sequence activity | One way, out | Sends, opens and replies log to the HubSpot contact timeline as calls, emails, meetings, tasks and notes. |
| HubSpot lists | One way, in | Lists feed Apollo for targeted prospecting, which is the direction teams forget exists. |
Two of those four rows move in both directions. The two that do not are Sequence activity and HubSpot lists, and those are the rows that decide how you design around this rather than the ones in the brochure.
The mapping is configurable in both directions, and two settings on it decide more than the field list does: what source gets written, and who ends up owning the record.
| In HubSpot | In Apollo | What to know about the match |
|---|---|---|
| An Apollo contact | A HubSpot contact | Pushed on your conditions, or all of them if you set none. |
| Apollo, as a value | The source property you choose | Defaults to Apollo. Picklist fields require you to select the value as well as the field. |
| The pushing user | HubSpot record ownership | Determined by whether that person has linked their own HubSpot credentials in Apollo, rather than by a setting on the integration. |
| A manual push | HubSpot, unconditionally | Overrides every sync setting, including stage restrictions and the other push limits you configured. |
| Push outcomes | Queue activity, Sync history and Error logs | Three separate views, and the only place a failed push is visible. |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: five field mappings and three documented exclusions, each one's note, and the two vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The manual-push override is the row that undoes the others: every careful condition you set is advisory the moment a rep clicks push on a profile.
Two choices rather than one. Apollo gates CRM integrations off its free plan entirely, and then asks you at authorisation which of two HubSpot integrations you actually want. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Apollo plan | HubSpot CRM | HubSpot Data Enrichment |
|---|---|---|
| Free | Not included | Not included |
| Basic or above | Two-way CRM sync | Enrichment only |
Counted off that grid, of four pairings: two give you not included, one gives you two-way CRM sync, one gives you enrichment only. Most people do not know the second column exists, because the decision arrives as a dropdown during an authorisation flow rather than as a question anybody asked.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Apollo: Settings, Integrations, HubSpot
Apollo offers two: HubSpot CRM for a full sync, and HubSpot Data Enrichment for enrichment only. They are different products behind one button, and picking the full sync because it sounds more capable is how prospecting data ends up in a CRM nobody agreed to put it in.
Nowhere. It is not shown as a countdown
On a paid Apollo plan, enabling the integration opens a six-hour window to configure sync settings and map fields. You cannot manually pull records during it, and when it expires syncing switches itself on. Settings remain editable afterwards, but the first sync will have run on whatever you had at hour six.
The HubSpot integration: Edit Conditions
You can push all new contacts, or restrict by contact stage, email verification status or a custom field. The verification condition is the one worth using: it is the difference between enriching your CRM and filling it with unverified prospecting data.
The contacts sync settings
Apollo writes a source onto every contact it pushes and defaults it to Apollo. You can point it at a different field, and if that field is a picklist you choose the value. This is your attribution, so decide it rather than inheriting it.
Per user, in Apollo
Ownership of a pushed contact depends on whether the person pushing has linked their own HubSpot credentials in Apollo. Without that link, records land under whatever the shared authentication produces, which is usually one admin owning everything.
The integration: Contacts, Push
Queue activity shows what is waiting, Sync history shows the runs, and Error logs shows what failed with a retry. That is where a failed push appears, not on the contact.
The six-hour window is the unusual part of this pair and the reason to read the whole setup before you click authorise: it is the only integration here with a timer attached to the configuration.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/hubspot-apollo/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-apollo.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyThe six-hour configuration window expired and Apollo enabled syncing automatically.
Adjust the settings now, in Settings, Integrations, HubSpot. The settings stay editable; what you cannot undo is the first run.
WhySomebody pushed them manually. Apollo documents that a manual push overrides the sync settings, including stage restrictions.
Treat the conditions as a default rather than a control, and train the team on what the push button on a profile actually does.
WhyThe pushing users have not linked their personal HubSpot credentials in Apollo, so ownership falls to the shared authentication.
Have each rep link their own credentials. Reassigning afterwards is possible and tedious.
WhyThe source field defaults to Apollo and was never changed.
Point it at the field your reporting uses, and pick the picklist value if that field is a picklist.
WhyIt failed, and the failure lives in the integration views rather than on the record.
Open Error logs under Contacts or Accounts, then Push, and retry from there. Queue activity shows what is still waiting.
WhyApollo's free plan excludes CRM integrations.
That is a plan question. The extension still works for manual research in the meantime.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
the duplicate thing killed us. we had contacts from 3 different sources (web forms, events, manual adds) all creating separate records
r/CRM·April 2026·4 points
Apollo is one of those sources once this integration is on, and the push conditions are what keep it from being the loudest. Restricting by email verification status before anything reaches the CRM is the setting that speaks to this directly.
I set something like this up with rate limits for the users in the hubspot account. This way you can break down ownership and territories at the source in apollo. Because with this, you are loading very cold leads into your sys
r/hubspot·May 2025·4 points
Exactly the right instinct and the right place for it. Ownership at the source is what the credential-linking step controls, and very cold leads reaching the CRM is what the push conditions exist to prevent.
Our HubSpot database is in bad shape right now. We have contacts missing job titles, incomplete company names, and outdated information from people who changed jobs months ago
r/CRMSoftware·January 2026·10 points
Worth noticing that this is the enrichment job rather than the prospecting one. Apollo offers both behind the same authorisation screen, and for this problem the Data Enrichment option is the one that does not also push new records in.
We are a 30+ sales team and we have been adding tools here and there but I feel like half of them barely talk to HubSpot
r/hubspot·April 2026·13 points
The useful question underneath it is which tools should write to the CRM rather than which can. This pair is unusually good at letting you answer that, through conditions, a source field and a choice of two integrations.
I replaced Apollo + Clay + Instantly + HubSpot with one outbound platform
r/microsaas·April 2026·18 points
Read it for the symptoms rather than the conclusion, since the writer is describing their own product decision. What drives posts like this is usually four tools writing to the same records with nobody owning the join, which is a configuration problem before it is a procurement one.
Few people discuss this pair directly, so the search widened to what teams do about enrichment and prospecting data reaching HubSpot. The recurring complaint is duplicates from several sources writing the same records, and the recurring instinct is to consolidate tools rather than to configure the ones they have. Both are relevant here, because this integration offers exactly the controls that prevent the problem and defaults to not using them.
The threads describe the problem this integration's settings are designed to prevent, which makes the six-hour window the thing to respect: it is the one chance to configure before the data starts arriving.
Most integrations in this directory move one kind of thing. This one moves three: records, activity and lists, in both directions. That is genuinely useful and it is also why the sync settings on this pair deserve an hour rather than a glance. A connector that can create contacts in your CRM from a prospecting database is a connector that can change what your CRM means.
The list direction is the underrated half. Teams set this up to get sequence activity onto the timeline, which is the obvious win, and then never notice that HubSpot lists can feed Apollo. A list is where your segmentation logic already lives, often after months of work. Pushing it into the prospecting tool instead of rebuilding the same filters there is the kind of small thing that quietly removes a weekly task.
The six-hour window is a real operational detail rather than a footnote. It is not a trial and it is not reversible by waiting: at the end of it, syncing turns on with whatever configuration exists. Read the sync settings first, know what you want each object to do, then enable, then configure. The order matters more than the configuration does.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under HubSpot, Apollo and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Yes. Contacts, accounts and deals move in both directions, sequence activity logs to the HubSpot timeline as calls, emails, meetings, tasks and notes, and HubSpot lists feed back into Apollo for targeting. That last direction is the one teams forget exists, and it saves rebuilding segmentation logic that already took months to get right.
After you enable the integration on a paid Apollo plan there is a six-hour period to configure sync settings and map fields, after which syncing enables itself with whatever configuration is in place. It is not a trial and waiting does not cancel it. Decide your settings first, then enable, at the start of a working day rather than on a Friday afternoon.
No. CRM integrations are excluded from the free tier. Basic, at $49 per user per month on annual billing, is where they start, and setup also needs Super Admin in HubSpot plus admin or CRM edit permissions in Apollo.
It can, and you should decide what qualifies before you map anything. A two-way sync between a prospecting database and your system of record means the prospecting database can create records, and without a rule the CRM fills with people nobody chose to contact and your reporting stops meaning much.
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.