---
name: hubspot-outreach-integration
description: Connect HubSpot and Outreach: what syncs, which editions carry it, the setup order, and the failures to expect. Covers contacts, activities. Use when the user wants to set up, audit or troubleshoot HubSpot and Outreach together, or asks why data is not moving between them.
---

# HubSpot and Outreach

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration
> Every tier requirement, sync direction and limit below was read from the vendors' own documentation on 2026-10-11.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**What you have to buy first:** An Outreach contract, and Super Admin or App Marketplace permissions in HubSpot. Custom field mappings need Data Hub.

**What moves:** contacts, activities, both ways.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

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.

## What needs Data Hub, and what does not

Rows: HubSpot subscription. Columns: What you are mapping. 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.

| HubSpot subscription | Standard field mappings | Custom field mappings |
|---|---|---|
| Any plan, no Data Hub | Included | Needs Data Hub |
| With Data Hub | Included | Included |

- **Included.** Contacts, email activity, engagement events and deals, syncing on the standard mappings, with the direction set per object. This is the whole integration for most teams.
- **Needs Data Hub.** A mapping to a field HubSpot does not provide as standard. Data Hub is sold separately from Sales Hub and is the same hub that gates the webhook and custom code workflow actions, so price it once for both.

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.

## What actually syncs

Direction is written from HubSpot's point of view: out means out of HubSpot, in means into it.

| What | Direction | What that means in practice |
|---|---|---|
| Contacts | Two-way sync | 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 | Two-way sync | 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 | Events only | Not supported. Outreach documents that it cannot sync individual records on demand with HubSpot. |

## Which field lands where

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

**What does not cross:**

- HubSpot email into Outreach. The email sync is one directional by design, so Outreach is never a complete record of what a prospect received.
- A prospect with no email address. Excluded by default, listed rather than errored.
- A single record on demand. Outreach documents that it cannot sync one record on request.

## Connect it, in this order

**Who has to do it:** A HubSpot Super Admin, or somebody with App Marketplace permissions. The Outreach side needs nothing beyond a contract.
**How long:** Twenty minutes to configure. Then days, potentially, for the first pass to finish.

### 1. Connect the app from the marketplace or the imports page

*Where:* 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.

### 2. Set the direction per object, not globally

*Where:* 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.

### 3. Decide now whether you need custom field mappings

*Where:* 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.

### 4. Set filters understanding what they do not do

*Where:* 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.

### 5. Save once, then leave it alone

*Where:* 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.

### 6. Check the Excluded column before declaring success

*Where:* 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.

## How to check it worked

- Create an Outreach prospect without an email address and confirm it never arrives, and that it appears in the Excluded column.
- Send an email from a mail client without the Outreach extension and check neither system logs it. That is the gap this integration does not close.
- Change a mapped field on each side and confirm which direction wins, per object.
- Wait out the initial sync before judging coverage. Several days is documented, not a fault.

## When it goes wrong

Each row is a symptom somebody reports, the documented reason, and the fix. Work down it before escalating to either vendor, because most of these are configuration.

| Symptom | Why it happens | What to do |
|---|---|---|
| Prospects are missing and nothing failed | They 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. |
| Opens and clicks are missing for some people | Event 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. |
| A rep insists they emailed somebody and neither system shows it | They 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. |
| The initial sync seems to have started over | Somebody 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. |
| A filter is not keeping records out | Filters 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. |
| A field will not map | It 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. |

## What breaks, from the vendors' own docs

- **Email sync is one way and narrow.** Only email sent with Outreach, from the app or from a mail client running the Outreach extension, reaches HubSpot. A rep who replies from Gmail without the extension has sent an email that exists in neither system's timeline, and nothing flags it. HubSpot email never travels to Outreach, so Outreach is not a complete record of what a prospect received.
- **Custom field mappings are a Data Hub feature.** Data sync runs on every HubSpot plan and custom field mappings need a Data Hub subscription. You can build and test one without the subscription, which is the cheapest way to find out whether your mapping genuinely needs it. If it does, price Data Hub before you commit to a go-live date, because it is the same hub that gates the webhook and custom code workflow actions and it is sold separately from Sales Hub.
- **No contact, no sync, and no error.** HubSpot matches contacts on email address and excludes records without one by default, and event sync only applies to contacts HubSpot already holds. So an Outreach prospect with no email, or engagement on somebody who has not reached HubSpot yet, simply does not appear. Records excluded this way are listed in the sync's Excluded column rather than raised as failures, and nobody looks at that column unless they already suspect something.
- **Saving the sync restarts the initial pass.** The initial sync indexes every record on both sides and HubSpot states that millions of records can take several days. Saving the configuration again starts that over. Filters only limit which records sync initially, so a record that has already come across keeps syncing on its field mappings whatever the filter now says, which is not what most people assume a filter does.

## The APIs, if you are building around it instead

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

## Filling the record this integration moves

The integration above moves a record between two systems. Neither of them creates what is in it, so a sync that works perfectly still carries whatever gaps the record arrived with. Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record through one API, and returns null with a confidence score rather than a guess.

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

## Sources

- Outreach support: HubSpot and Outreach FAQ: https://support.outreach.io/support/solutions/articles/159000425625
- Outreach support: can I connect Outreach and HubSpot via data sync by HubSpot?: https://support.outreach.io/support/solutions/articles/159000426013-can-i-connect-outreach-and-hubspot-via-data-sync-by-hubspot-
- HubSpot knowledge base: connect and use HubSpot data sync: https://knowledge.hubspot.com/integrations/connect-and-use-hubspot-data-sync
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-outreach-integration

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
