Contacts both ways, email one way, and HubSpot rather than Outreach owns it.
An Outreach contract, and Super Admin or App Marketplace permissions in HubSpot. Custom field mappings need Data Hub.
Contacts, Activities, two-way sync.
The thing to understand before anything else is who built this: Outreach wrote a deep native plugin for Salesforce and did not write one for HubSpot; the HubSpot pairing runs on HubSpot data sync, so HubSpot owns the code and Outreach points sync problems at HubSpot support. Read that as a scoping fact rather than a complaint. You get a contact sync whose direction you choose and email activity flowing one way into HubSpot, which covers what most teams want. You do not get per-object polling, per-field outbound control or task and event mapping, and if your evaluation was based on how this works against Salesforce you are comparing two different products.
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 | Both ways | One way or two way, set in HubSpot. Matched on email address, and contacts with no email are excluded unless you turn that off. |
| Email activity | One way, in | Outreach to HubSpot only, and only for email sent from Outreach or a client running its extension. |
| Engagement events | One way, in | Opens and clicks flow one way from the app into HubSpot, and only for contacts HubSpot already holds. |
| Deals | Both ways | Only where you map pipelines and stages, and only deals sitting in a mapped stage. |
| HubSpot email into Outreach | One way, out | Nothing. Email sync is one directional by design, not by configuration. |
| A single record on demand | Event only | Not supported. Outreach documents that it cannot sync individual records on demand with HubSpot. |
Two of those six rows move in both directions. The three that do not are Email activity, Engagement events and HubSpot email into Outreach, and those are the rows that decide how you design around this rather than the ones in the brochure.
This runs on HubSpot data sync rather than on a bespoke connector, so the behaviour is HubSpot's rather than Outreach's. Two of its rules decide most of what people find surprising.
| In HubSpot | In Outreach | What to know about the match |
|---|---|---|
| Contacts | Contacts, matched on email address | Direction configurable per object. Email is the match key, which is why records without one go nowhere. |
| Email sent with Outreach | HubSpot activity | One way only, and only email sent from Outreach or from a mail client running the Outreach extension. |
| Opens and clicks | HubSpot, for contacts it already holds | Event sync applies only to existing HubSpot contacts, so engagement on a prospect who has not crossed yet is invisible. |
| Deals | Opportunities, where you map pipelines and stages | Mapping stages between two pipelines designed separately is the work on this half. |
| A custom field mapping | Only with Data Hub | Standard mappings are included on every HubSpot plan; custom ones are a separate subscription. |
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 three 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 email asymmetry is the one to communicate to the team rather than to configure around: a rep replying from Gmail without the extension has sent something that exists in neither timeline.
This pair has one gate and it is narrower than people fear. Data sync itself runs on every HubSpot plan, including free. What a subscription buys is the ability to map a field that is not standard. Pick one on each side and the grid marks the answer.
Pick one on each side.
| HubSpot subscription | Standard field mappings | Custom field mappings |
|---|---|---|
| Any plan, no Data Hub | Included | Needs Data Hub |
| With Data Hub | Included | Included |
Counted off that grid, of four pairings: three give you included, one gives you needs Data Hub. Build the mapping you want first and see whether it fits the standard set. It is a free test of an expensive question, and it is the only question this grid asks.
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.
HubSpot: Marketplace, or Import on any object home page
Both routes reach the same place. Super Admin or App Marketplace permissions are required, which is the only permission gate on this pair.
The sync configuration: the arrows dropdown
Each object sync is bi-directional, app to HubSpot, or HubSpot to app. Contacts can be two-way while everything else is one-way, and that is usually the right answer rather than a compromise.
The field mapping screen
Standard mappings work on every HubSpot plan. Custom field mappings need a Data Hub subscription, sold separately from Sales Hub. You can build and test a mapping without the subscription, which is the cheapest way to find out whether yours genuinely needs it.
The sync configuration: filters
A filter limits which records sync initially. A record that has already crossed keeps syncing on its field mappings whatever the filter says afterwards, which is not what most people assume a filter means.
The sync configuration
The initial sync indexes every record on both sides, and HubSpot says millions of records can take several days. Saving the configuration again restarts that pass, so the instinct to tweak and re-save is expensive here.
The sync overview
Records without an email address are excluded by default rather than failed, and they appear in a column nobody opens unless they already suspect something. Look at it on day one, while you still remember what you expected.
The two steps that cost the most if skipped are both about expectations rather than settings: what a filter actually filters, and where excluded records go.
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-outreach/SKILL.md https://www.reversecontact.com/integrations-hub/skills/hubspot-outreach.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.
WhyThey have no email address. HubSpot matches contacts on email and excludes records without one by default.
Open the Excluded column on the sync. These are listed there rather than raised as errors, which is why nobody finds them.
WhyEvent sync only applies to contacts HubSpot already holds, so engagement on a prospect who has not synced yet has nowhere to land.
Get the contact across first. The events do not backfill once it arrives.
WhyThey sent it from a mail client without the Outreach extension. Only email sent through Outreach or through a client running the extension reaches HubSpot.
This is a training and extension-deployment problem rather than a sync one. Nothing flags the gap.
WhySomebody saved the configuration again. HubSpot restarts the full index when you do.
Decide the configuration, save once and wait. Several days is documented for large record counts.
WhyFilters limit which records sync initially. A record already synced keeps syncing on its field mappings regardless.
Filter before the first pass, or unsync the records individually. Changing the filter later does not reach back.
WhyIt is not a standard mapping, and custom field mappings need a Data Hub subscription.
Confirm by building the mapping, which you can do without the subscription. If it needs Data Hub, price that before committing to a go-live date.
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.
We have been trying to clean up our sales stack, and the biggest headache has been finding an outreach tool that does not break every time
r/CRMSoftware·November 2025·5 points
On this pair the join does not break; it just carries less than people assume. The email sync is one way and covers only mail sent through Outreach, and that is the thing to check against your own expectations before switching tools again.
Salesloft is a solid product in an of itself, and I see a lot of organizations use it successfully (they have some really cool research out there about sequence cadence), but you hit the nail on the head in terms of conn
r/hubspot·March 2024·5 points
Which is the honest comparison for a HubSpot shop choosing a sequencer. Outreach reaches HubSpot through HubSpot's own data sync rather than a bespoke connector, so the behaviour is predictable and documented, and the limits are HubSpot's.
I think true inbound only is dead. It is increasingly expensive to do well and ROI has diminished significantly over the years. Nearly every brand I know uses HubSpot for outbound.
r/hubspot·January 2025·5 points
Which is why this pair matters more than its search volume suggests. If outbound activity is going to drive HubSpot reporting, the one-directional email sync is a reporting decision rather than a technical footnote.
My company uses salesforce primarily but I prefer using hubspot to run email outreach campaigns. I am wondering how can I map my hubspot progress into salesforce.
r/salesforce·May 2025·7 points
A different pair, and the same instinct that drives this one. The question to answer first is which system the activity has to be reportable in, because that decides the direction of every sync on this page.
I am currently using HubSpot for my marketing and sales processes, and I am looking to improve my email outreach and lead management strategy
r/hubspot·January 2025·12 points
The specific thing worth knowing before buying Outreach for a HubSpot stack: the integration is HubSpot data sync, it is free on every plan unless you need a custom field mapping, and it will not carry HubSpot email back into Outreach.
Nobody writes about configuring this pair, so the search was for the decision in front of it: which outreach tool to put next to HubSpot. The threads are full of people choosing, and the criterion they name is not features but whether the connection holds. That is a reasonable thing to ask of this pair, whose answer is that it holds and is narrower than you expect.
The threads ask whether the connection holds and this one does, which moves the real question to coverage: decide what you need in HubSpot's timeline before you decide which sequencer writes it.
Almost every difficult conversation about this pair comes from comparing it to the wrong thing. Outreach built a deep, configurable plugin for Salesforce, with per-object polling, per-field outbound toggles and conditions on what pushes, and teams reasonably assume the HubSpot integration is that product aimed at a different CRM. It is not: HubSpot built this one on its own data sync engine, and Outreach's documentation is explicit that HubSpot engineers manage it and HubSpot support handles sync issues. Everything that follows is downstream of that single fact.
What you get is genuinely useful and worth setting up: contacts moving in the direction you chose, matched on email, with sequence email and engagement landing on the HubSpot timeline. What you do not get is an audit trail of everything a prospect received, because only mail sent through Outreach or its extension travels, and nothing travels the other way. The practical consequence is a rule rather than a setting: if you want the CRM to be the record of truth for conversations, reps have to send from Outreach or from a client running the extension, and that is a habit to enforce before go-live rather than a gap to discover in a QBR.
The cost question has two halves and only one of them is obvious: Outreach has no free tier, so the licence is the visible number. The hidden one is Data Hub, which custom field mappings require, and which is the same hub that carries the webhook and custom code workflow actions HubSpot sells separately from Sales Hub. HubSpot lets you build and test a custom mapping without the subscription, so spend an afternoon finding out whether your mapping needs it before anyone quotes for it. If it does, compare that price against the CRM data layer build, which moves the same fields through Clay or n8n and is the cheaper answer more often than teams expect.
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, Outreach 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, and it is not the one Outreach built for Salesforce. Outreach and HubSpot connect through HubSpot data sync, which means HubSpot wrote it, HubSpot runs it, and Outreach's own documentation sends you to HubSpot support for sync problems. That is a reasonable arrangement and it changes what you should expect: this is a contact sync with configurable direction, not the per-object, per-field plugin with its own polling that Outreach ships for Salesforce.
Contacts, one way or two way, as you choose in HubSpot. Emails sync in one direction only, from Outreach into HubSpot, and only emails sent with Outreach from the app or from a mail client running the Outreach extension. Mail sent any other way does not come across, and HubSpot email does not go to Outreach at all. There is no on-demand sync of a single record, which surprises people who want to force one prospect through before a call.
Data sync itself runs on all products and plans, and you need to be a Super Admin or hold App Marketplace permissions to connect it. The gate is custom field mappings, which require a Data Hub subscription. You can test a custom mapping without one, which is a genuinely useful way to find out whether you need the hub before buying it. On the Outreach side there is no free tier, so the licence is the real cost on this pair.
HubSpot checks for changes every five minutes and the connected app signals its own changes by webhook, so after the initial sync a changed record moves within about ten minutes. The initial sync is the slow part: HubSpot indexes every record on both sides first, and states that databases with millions of records can take several days. Saving the sync again restarts that initial pass, which is worth knowing before you tweak a setting on a Friday.
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.