ZoomInfo integrations

ZoomInfo integrations, and the edition each one needs

Three integrations, and on two of them the edition is the feature. There is no configuration that moves a capability down a tier, so the evaluation question is which edition you are on rather than how you set it up.

zoominfo.com 3 integrations
layerData, Prospecting
entryQuote only
authAPI key or OAuth, depending on p...
automationInbound Enrich, scheduled bulk e...
verified2026-09-18
checked Guides written 3 of 3
3integrations checked
2built natively
0sync both ways
3need a plan upgrade
The short version

What decides a ZoomInfo integration

Deep native CRM integrations, sold by tier.

ZoomInfo is quoted per seat and per package, with no free tier and no published rate card, so nothing on this hub has a price you can look up. What is published is which edition carries which feature, and that is the decision. Native HubSpot sync starts at Advanced, and two-way sync with intent fields is Elite, with no setting that moves either one down.

The second thing these pages keep saying is that enrichment is a write. Field mapping is the whole configuration: point ZoomInfo at a property a rep maintains and ZoomInfo wins, which is why the HubSpot pair spends longer on mapping than on connecting. On Salesforce the default is sharper still, because Person Has Moved rewrites a contact to their new employer unless somebody turns it off.

The meter is the third thing, and it is unlike the rest of this directory. ZoomInfo charges one credit the first time it enriches a record in a rolling twelve months and then places that record under management for the year, so the unit is a record rather than a call. The Reverse Contact comparison is the page that puts the two meters side by side, because that difference decides more builds than coverage does.

ZoomInfo sits in 2 of the seven layers this directory splits a stack into, the data layer and the prospecting layer among them, which is why it turns up in so many pairs. Counted across the whole directory it reaches 3 of the other 22 tools, and the integration matrix shows that row against every other.

All 3

Every ZoomInfo integration, with what it moves

Start with how the integration is built, because a native app and a webhook you maintain are the same feature with completely different owners.

The data layer

Whichever of these you connect, the integration moves the record. We fill it.

Start for free
Showing 3 of 3
Buyer's guide

How to pick, and what to check first

4 things that decide whether a ZoomInfo integration will work for you, in the order they usually bite.

01

The edition is the integration

Native HubSpot sync starts at ZoomInfo Advanced, and two-way sync and intent fields are Elite. There is no configuration that moves a feature down a tier, which makes the evaluation unusually simple and unusually expensive. The Salesforce side needs ZoomInfo Sales with Enrich, the AppExchange package and a Salesforce edition with API access. Ask which edition the quote covers before asking what the integration can do.

02

Enrichment overwrites, by design

Field mapping is the configuration here, and the default direction is that ZoomInfo wins. Pointing it at a property a rep maintains will flatten what the rep knew, so the advice on these pages is to map to dedicated ZoomInfo properties and let your own workflows decide what gets copied across. Keep enrichment away from source fields as well, because anything writing on record creation sits close to what original-source attribution depends on.

03

Person Has Moved is on unless you turn it off

On Salesforce, a contact who changed jobs is enriched to their new organisation inside your CRM, because the setting is enabled by default. That is either exactly what you want or a quiet rewrite of your account history, and which one depends on whether your reporting treats a contact as a person or as a relationship with a company. Decide before the first run rather than after it.

04

A smaller batch costs more, and the sandbox is not free

Instant Enrich spends two Salesforce API calls per record, one to read the existing values so the update option can be honoured and one to write. Scheduled Enrich runs through the Bulk API in batches of 10,000 by default, and ZoomInfo is explicit that reducing the batch size increases the number of API calls. Running Enrich in a sandbox incurs bulk credit charges exactly as production does. Test in small batches knowing that the test itself is billed.

Written up

The ZoomInfo integrations with a full guide

Each one covers what syncs in which direction, the tier it needs, the limits that bite, when not to use it, and the questions people ask before they start.

Other tools

Integrations for the rest of the stack

Connecting ZoomInfo is half the job

An integration moves a record from one system to another. It does not make the record worth moving. Reverse Contact is the layer underneath: one API that resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score instead of a guess.

Free trial, no card required, and 500 credits to start.

FAQ

ZoomInfo integrations, asked and answered

The questions that come up before anyone opens a setup guide.

Which ZoomInfo edition do I need for the HubSpot integration?

Advanced for the native sync, and Elite if you want two-way sync or intent fields. ZoomInfo documents these as edition features rather than configuration, so there is no setting that enables them lower down. The Salesforce route needs ZoomInfo Sales with Enrich plus the AppExchange package and a Salesforce edition that includes API access.

How does ZoomInfo charge for enrichment?

By record rather than by call. The first time a record is enriched within a rolling twelve-month period it consumes one credit and the record is placed under management for a year, so re-enriching it inside that window costs nothing further. Several operations consume no credits at all, including Lookup, Search Companies, Search Contacts, Find Similar Companies, Find Similar Contacts and Find Recommended Contacts.

What are the ZoomInfo API rate limits?

They depend on the package, and there are three windows checked at once. Standard is 25 requests a second, 54,000 an hour and 648,000 a day; Builder is 5, 10,800 and 129,600; Scaling is 35, 75,600 and 907,200. The hour and day windows are rolling rather than calendar, and the package names are published while the price is not.

Where is the ZoomInfo API documentation?

It moved. docs.zoominfo.com now returns a permanent redirect to docs.gtm.ai, so a bookmark or a citation from before the move lands on a 301 rather than on the page. Every ZoomInfo figure on this hub was read after that move. Two ZoomInfo pages also disagree about which rate-limit headers come back on a response, with an older pair marked deprecated and due for removal on 2027-01-01.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit behind the 3 integrations on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-09-18
Sources
6 vendor documents
Paid placement
None

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.

Ask an assistant