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

# HubSpot and ZoomInfo

> Generated from https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-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:** ZoomInfo Advanced for the native sync, Elite for two-way sync and intent fields

**What moves:** contacts, companies, lists, one way, into HubSpot.
**How it is built:** native, marketplace app. **Effort:** hours.

## The short version

Inbound Enrich is the part worth buying. A record appears in HubSpot from a form, an import or a rep typing it, and it comes back filled in, with field mapping you control so it does not flatten what someone already entered. The parts teams assume are included, two-way sync and intent fields, sit on Elite. Price this on the edition rather than on the integration, because the integration costs nothing and the edition is most of your bill.

## Which edition carries this, and whose

Rows: ZoomInfo edition. Columns: HubSpot plan. ZoomInfo lists Free, Basic, Professional and Enterprise as supported HubSpot plans, so the columns below are identical on purpose: HubSpot gates nothing here. The gate is entirely ZoomInfo's, and ZoomInfo quotes rather than publishes, which is why the rows are the expensive axis.

| ZoomInfo edition | Free or Starter | Professional | Enterprise |
|---|---|---|---|
| Below Advanced | No native sync | No native sync | No native sync |
| Advanced | One-way enrichment | One-way enrichment | One-way enrichment |
| Elite | Plus two-way sync and intent | Plus two-way sync and intent | Plus two-way sync and intent |

- **No native sync.** The native integration is not available. Whatever HubSpot plan you hold makes no difference to this row.
- **One-way enrichment.** Inbound Enrich as records are created, scheduled enrichment over the back catalogue, and export from ZoomInfo into HubSpot. One direction.
- **Plus two-way sync and intent.** The same, plus two-way sync and intent fields, which are the features teams most often assume are included.

Counted off that grid, of nine pairings: three give you no native sync, three give you one-way enrichment, three give you plus two-way sync and intent.

Reading this grid horizontally is the point: moving along a row buys you nothing, so an upgrade conversation with HubSpot will not fix a capability gap here, and the only lever is a renegotiation with ZoomInfo.

## 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 |
|---|---|---|
| New contacts | One way, in | Enriched on creation with title, department, seniority and contact fields, subject to your mapping. |
| New companies | One way, in | Firmographics written to company properties on creation. |
| Existing records | One way, in | Scheduled bulk enrichment keeps the back catalogue current rather than only new rows. |
| Account lists | One way, in | With Copilot and Account Fit Score, high-fit accounts can push into HubSpot lists on a daily schedule. |
| Everything back to ZoomInfo | Two-way sync | Elite only. On Advanced this integration is a one-way enrichment pipe. |

## Which field lands where

Mapping is explicit and per field, with its own behaviour on each. The part that surprises people is that company mapping is configured in the same screen as contact mapping and fails independently of it.

| In HubSpot | In ZoomInfo | What to know about the match |
|---|---|---|
| A ZoomInfo contact field | The HubSpot contact property you choose | With an export behaviour set per field, which is where overwrite is decided. |
| A ZoomInfo company field | The HubSpot company property you choose | Configured alongside contacts and reported in the wild as populating less reliably. Test companies separately. |
| A record ZoomInfo matches to an existing one | A duplicate flag at export time | The rep then chooses from whatever options the admin left available, including creating the duplicate anyway. |
| Your HubSpot data | ZoomInfo, for analysis | HubSpot Import is enabled by default and lets ZoomInfo import and analyse information about your team, prospects and customers. |

**What does not cross:**

- Anything, if the connecting account cannot see it. Permissions on the service account cap the whole integration.
- Intent and two-way sync, below the ZoomInfo edition that carries them. Those are a contract question rather than a configuration one.

## Connect it, in this order

**Who has to do it:** A ZoomInfo admin with the Admin Portal, and a HubSpot Super Admin or an admin carrying the CRM object permissions below.
**How long:** An afternoon, and one decision at the start that is awkward to change later.

### 1. Choose the connection model before anything else

*Where:* ZoomInfo Admin Portal

ZoomInfo offers a service account connection, which is the default and its preferred option, or individual user account connections. With a service account every export and every HubSpot filtering job runs through one account, which is why ZoomInfo recommends it: nobody has to troubleshoot a departed rep's connection.

### 2. Set the HubSpot permissions on whichever account connects

*Where:* HubSpot: Settings, Users and Teams, Edit permissions

Under CRM objects, contacts need View, Edit and Delete. ZoomInfo gives a minimum of "contacts they own" and recommends "all contacts", and the same pattern applies to companies. A service account on the minimum will quietly export less than you asked for.

### 3. Make the admin connection

*Where:* ZoomInfo Admin Portal: Integrations, HubSpot

Connect as a HubSpot Super Admin, or as an admin user holding the permissions above. Everything after this inherits that account's reach.

### 4. Decide what HubSpot Import is allowed to do, because it is on by default

*Where:* Integration settings: HubSpot Import

ZoomInfo documents this as enabled by default, letting it import and analyse information about your team and your prospects and customers from HubSpot. Whether that is fine is a question for whoever owns your data agreements, and the default answers it for them unless somebody looks.

### 5. Configure export mapping field by field, with behaviour per field

*Where:* Integration settings: Export Mapping

Each ZoomInfo field is paired with a HubSpot field and given a behaviour for export. This is where enrichment either respects what a rep typed or flattens it, and it is the step people skim.

### 6. Set the duplicate policy as an admin rather than leaving it to reps

*Where:* Admin Portal: duplication settings

The admin sets the default behaviour when an export hits a duplicate. Reps are then shown the flag during export and can update the existing record, create a duplicate, or take whichever other options you left open. Leaving all of them open means the CRM's duplicate policy is decided one rep at a time.

### 7. Turn it on for users last

*Where:* Admin Portal: user enablement

Only after mapping and duplicate settings are agreed. Enabling export first and configuring afterwards means the first week of exports was the test run, in production.

Two of those seven are the ones to get right: the connection model, which decides who can fix it later, and the duplicate policy, which decides what the CRM looks like in six months.

## How to check it worked

- Export five contacts and five companies. Companies fail separately from contacts on this pair, and testing only contacts is how that gets missed.
- Export somebody you know is already in HubSpot and watch the duplicate flag appear. If it does not, the policy is not doing what you think.
- Check a field a rep owns after an export, to confirm the export behaviour on that mapping is not overwriting it.
- Read the HubSpot Import setting and write down who decided it, because it is on unless somebody turned it off.

## 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 |
|---|---|---|
| Contact fields populate and company fields do not | Company mapping is configured in the same place and behaves independently, and practitioners report exactly this asymmetry with mappings that look correct in the Admin Portal. | Check the connecting account's permissions on companies specifically, not just on contacts, then re-test with a single company export. |
| Exports reach fewer records than expected | The connecting account is on the minimum permission of records they own rather than all records. | Raise the permission to the recommended level on both contacts and companies. ZoomInfo documents both the minimum and the recommendation, and the gap between them is silent. |
| Duplicates are piling up after exports | The admin left the create-a-duplicate option available, and reps in a hurry take it. | Restrict the duplicate options in the Admin Portal so updating the existing record is the path of least resistance. |
| The integration broke when somebody left the company | Individual user account connections tie the integration to people. | Move to the service account connection, which ZoomInfo describes as the default and preferred option for exactly this reason. |
| Nobody authorised ZoomInfo to read the CRM | HubSpot Import is enabled by default and allows ZoomInfo to import and analyse information from HubSpot about your team and your prospects and customers. | Decide it deliberately and record who decided. This is a data-sharing setting rather than a performance one, so the person to ask is not the CRM admin. |
| Reps complain the data overwrote their notes | Export behaviour on those field mappings. | Change the behaviour per field. The mapping screen allows it and the default is not always what a rep would choose. |

## What breaks, from the vendors' own docs

- **The edition is the integration.** Native HubSpot sync starts at ZoomInfo Advanced. Two-way sync and intent fields are Elite. There is no configuration that moves a feature down a tier, so the evaluation question is which edition, not which integration.
- **Enrichment is a write, and writes overwrite.** Field mapping is the whole configuration here. Point ZoomInfo at a property a rep maintains and it will win. Map to dedicated ZoomInfo properties and let your workflows decide what gets promoted to the fields people trust.
- **Watch what it does to source reporting.** Anything that writes to a record on creation sits close to the properties original-source attribution depends on. Keep enrichment away from source fields unless you have decided, deliberately, that it should own them.
- **It needs admin on both sides.** Setting up the native integration requires admin access in HubSpot and in ZoomInfo. On the ZoomInfo side that is usually the person who owns the contract, not the person who uses it.

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

- ZoomInfo University: integrations and implementations: https://university.zoominfo.com/page/integrations-implementations
- ZoomInfo: HubSpot integration guide (PDF): https://tech-docs-library.zoominfo.com/hubspot-integration-guide.pdf
- 14 practitioner threads read on 2026-10-11, summarised on the page: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-integration#reddit
- This pair, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-zoominfo-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.*
