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

# HubSpot and Apollo

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-apollo-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:** Apollo Basic or above. The free plan excludes CRM integrations.

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

## The short version

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.

## Which plan carries it, and which integration you picked

Rows: Apollo plan. Columns: What you authorise. 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.

| Apollo plan | HubSpot CRM | HubSpot Data Enrichment |
|---|---|---|
| Free | Not included | Not included |
| Basic or above | Two-way CRM sync | Enrichment only |

- **Not included.** Apollo's free plan excludes CRM integrations. The browser extension still works, which is why teams on free plans end up doing this by hand.
- **Two-way CRM sync.** The full integration: pushing contacts and accounts on your conditions, pulling from HubSpot, field mapping in both directions.
- **Enrichment only.** Enrichment of records that are already in HubSpot, without Apollo pushing its own prospecting data in. For a team worried about what lands in the CRM, this is the safer half and it is a choice made once, at authorisation.

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.

## 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 and accounts | Two-way sync | Push from Apollo into HubSpot with mapped fields, and pull HubSpot records into Apollo. |
| Deals | Two-way sync | 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. |

## Which field lands where

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

**What does not cross:**

- Anything, on the Apollo free plan. CRM integrations are excluded from it.
- The sync conditions, when somebody pushes by hand. A manual push bypasses all of them by design.
- Records you wanted to pull during the first six hours. Manual pulls are blocked for the length of the configuration window.

## Connect it, in this order

**Who has to do it:** An Apollo admin and a HubSpot Super Admin. Each rep who wants their own records attributed to them links their own HubSpot credentials afterwards.
**How long:** The clock is six hours and it starts the moment you authorise, so do this when you have the afternoon.

### 1. Choose which integration you are authorising

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

### 2. Know that a six-hour timer just started

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

### 3. Set the push conditions before the timer runs out

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

### 4. Set the source field deliberately

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

### 5. Decide how ownership is assigned

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

### 6. Map fields, then check the queue rather than the records

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

## How to check it worked

- Push one contact manually and check which HubSpot user owns it. That tells you whether credential linking is set up before 400 contacts arrive under an admin.
- Check the source property on that contact. If it says Apollo and you wanted something else, the source field is still at its default.
- Set a stage restriction, then deliberately push a record that fails it. A manual push ignores sync settings entirely, which is worth seeing once.
- Open Error logs after the first scheduled run rather than waiting for somebody to report a missing contact.

## 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 |
|---|---|---|
| Syncing started before anybody was ready | The 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. |
| Contacts arrived that should have been filtered out | Somebody 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. |
| One admin owns every contact Apollo created | The 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. |
| Every Apollo contact has the same source | The 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. |
| A push silently did nothing | It 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. |
| The integration is not available at all | Apollo's free plan excludes CRM integrations. | That is a plan question. The extension still works for manual research in the meantime. |

## What breaks, from the vendors' own docs

- **Six hours to configure.** On a paid plan, enabling the integration starts a six-hour window to configure sync settings and map fields before syncing is automatically enabled. Whatever the defaults are at the end of that window is what runs. Do not enable it on a Friday afternoon.
- **The free plan does not include it.** CRM integrations are excluded from Apollo's free tier. Basic, at $49 per user per month on annual billing, is the entry point for this pair.
- **It needs Super Admin in HubSpot.** Plus admin or CRM edit permissions in Apollo. Standard for a two-way connector, and worth lining up before the six-hour clock starts.
- **Pushing prospecting data into the CRM is a decision.** A two-way sync between a prospecting database and your system of record means Apollo can create records. Decide what qualifies for creation before you map anything, or the CRM fills with people nobody chose to contact.

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

- Apollo knowledge base: HubSpot integration overview: https://knowledge.apollo.io/hc/en-us/articles/19745130546573-HubSpot-Integration-Overview
- Apollo knowledge base: configure HubSpot sync settings: https://knowledge.apollo.io/hc/en-us/articles/4416606988941-Configure-HubSpot-Sync-Settings
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-apollo-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-apollo-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.*
