---
title: "ZoomInfo API and HubSpot: When to Build a Custom Integration"
description: "ZoomInfo API and HubSpot: when the native integration is enough, when custom wins, three architectures, credit control, auth basics and upkeep costs."
---

[Go-To-Market Blog | Quantum Business Solutions](https://www.thequantumleap.business/blog)

# [ZoomInfo API and HubSpot: When to Build a Custom Integration](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration)

 Written by [Shawn Peterson](https://www.thequantumleap.business/blog/author/ceo) | Nov 22, 2026, 4:29:50 PM

## TL;DR: Quick Answer

Use the native ZoomInfo HubSpot integration until you hit a wall it cannot get past: custom objects, enrichment that must fire at a precise moment under business rules, or ZoomInfo data the integration does not write. At that point a small custom build on the ZoomInfo API, run from HubSpot custom code actions or a middleware service, usually beats bending the native app.

- ZoomInfo API search is free; enrich costs one bulk data credit per new record, and the record stays free to re-enrich for 12 months.
- Server-to-server builds use OAuth 2.0 client credentials with a named integration user.
- The real cost of custom is maintenance: runtimes, API changes, monitoring and an owner.

This guide is for the RevOps lead or technical owner deciding whether to keep living with the native ZoomInfo HubSpot integration or build something on the ZoomInfo API. You will get a test for when native is enough, the cases where custom wins, the three architectures we see work, how to keep credits under control, the authentication basics and an honest view of what a custom build costs to keep running. For the integration as a whole, start with our [ZoomInfo HubSpot integration guide](https://www.thequantumleap.business/blog/zoominfo-hubspot-integration-guide).

## Table of Contents

1. [When is the native integration enough?](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#native-enough)
2. [When does a custom integration win?](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#custom-wins)
3. [What the ZoomInfo API gives you](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#what-the-api-offers)
4. [Three architecture options](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#architecture)
5. [What does a typical custom flow look like?](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#pseudo-flow)
6. [How do you control credits in a custom build?](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#credits)
7. [Authentication and rate limit basics](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#auth)
8. [What does custom cost to maintain?](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#maintenance)
9. [Conclusion](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#conclusion)
10. [Frequently Asked Questions](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration?hs_amp=true#faq)

## When is the native integration enough?

For most HubSpot teams, native is enough. "Native" covers two separate ZoomInfo products, and it helps to name them:

- **The ZoomInfo platform integration**, connected in the ZoomInfo Admin Portal. It exports companies and contacts to HubSpot with field mapping, a "Complete if missing" or "Overwrite field" rule per field, duplicate checks (domain for companies; email, then name plus exact company name for contacts), and automated exports through ZoomInfo Workflows.
- **ZoomInfo Inbound Enrich**, the HubSpot Marketplace app. It enriches contacts as they are created in HubSpot, can enrich companies, and needs its own Inbound Enrich subscription.

If your needs are "get good records in, keep standard company and contact fields filled, and route on them", stay native. Our [field mapping template](https://www.thequantumleap.business/blog/zoominfo-hubspot-field-mapping) and [enrich mode guide](https://www.thequantumleap.business/blog/zoominfo-enrichment-hubspot) get most teams there without code.

## When does a custom integration win?

Custom wins when the requirement is about **where** data lands, **when** enrichment fires or **which** data you need. These are the cases we see most:

| Requirement | Why native struggles | Custom approach |
| --- | --- | --- |
| Write to a custom object, such as sites, locations or equipment | The platform export is configured for companies and contacts | Enrich via API, then write to the custom object with HubSpot's API |
| Enrich only after a rule passes (lifecycle stage, score, no open deal) | Native enrichment runs on its own triggers and schedules | A HubSpot workflow decides, a custom code action calls ZoomInfo |
| Data the integration does not map, such as corporate hierarchy, org charts or technologies as rows | Export mapping targets standard fields | Call the specific enrich endpoint and store results where you need them |
| Parent and child accounts across many sites | Domain matching treats one domain as one company | Match on ZoomInfo company ID and hierarchy, then associate |
| One ZoomInfo contract feeding several HubSpot portals or a warehouse | Each connection is set up per destination | Middleware enriches once and writes everywhere |

If none of these apply, the native integration plus good settings will beat custom on cost every time.

## What the ZoomInfo API gives you

ZoomInfo's current developer documentation groups its Data API into search, enrich and lookup. Your package decides which scopes and endpoints you can call.

| Group | Examples | Credit impact |
| --- | --- | --- |
| **Search** | Contacts, companies, intent, news, scoops | Free; returns matches, not full contact details |
| **Enrich** | Contacts and companies (up to 25 records per request), corporate hierarchy, intent, news, org charts, technologies, hashtags | One bulk data credit per new company or contact record; intent enrich uses credits |
| **Lookup** | Valid values for search and enrich fields | Free |
| **Usage** | Your API usage and limits | Free |

Intent search and intent enrich need the Intent SKU on your contract. ZoomInfo also documents APIs for GTM Studio audiences, data quality and agents, plus an MCP server, which our post on [using ZoomInfo data inside AI assistants](https://www.thequantumleap.business/blog/zoominfo-mcp-use-data-inside-ai-assistants) covers.

## Three architecture options

Pick the lightest option that meets the requirement. Each step up adds capability and adds something to maintain.

### 1. HubSpot custom code action

A HubSpot workflow enrolls the record, checks your rules, then a custom code action (JavaScript or Python) calls ZoomInfo and returns values the workflow writes back. It needs Data Hub Professional or Enterprise. HubSpot limits each run to 20 seconds and 128 MB of memory, stores your ZoomInfo credentials as secrets, and lets you rate-limit the action. Best for record-at-a-time enrichment under business rules.

### 2. Middleware or a small service

A scheduled job or integration platform pulls a batch from HubSpot, searches and enriches in ZoomInfo, and writes back through HubSpot's API, including custom objects (which need HubSpot Enterprise). Best for volume, custom objects and multi-portal setups.

### 3. Hybrid

Keep the native integration for exports and standard fields, and use the API only for the one job it cannot do, such as hierarchy into a custom object. In our experience this is where most well-run teams end up.

### Not sure whether you need custom at all?

We will look at your requirement and your current integration settings and tell you whether native can do it. [Book a free 30-minute fit check](https://meetings.hubspot.com/shawn-peterson/quantum-website).

## What does a typical custom flow look like?

Here is the shape of a rule-gated enrichment we would build with option 1. No code, just the logic.

1. **Trigger in HubSpot:** a company reaches a target lifecycle stage and has a domain.
2. **Gate:** skip if "ZoomInfo last enriched" is within 12 months or the domain is a free email provider.
3. **Match:** if the record has a stored ZoomInfo company ID, use it; otherwise send the domain and name to enrich.
4. **Enrich:** request only the fields you will store.
5. **Write back:** fill properties that are empty, overwrite only the fields you have decided ZoomInfo owns, and stamp the ZoomInfo ID and the enrichment date.
6. **Handle failure:** on no match, set a "ZoomInfo no match" flag so the record is not retried every day. On 429 or 5xx errors, let it retry.

Steps 2 and 6 are where custom builds save or waste money. HubSpot will retry a custom code action that throws on a 429 or 5xx response for up to three days, so a missing no-match flag turns into repeat calls quickly.

## How do you control credits in a custom build?

ZoomInfo's API documentation is clear on the rules: search, lookup and find-similar calls are free. Enriching a company or contact uses one bulk data credit the first time in a rolling 12-month period, and the record is then "under management" for a year, so enriching it again in that window does not use another credit. Each enrichment still counts against your record limit.

- **Search first, enrich second.** Search is free. Only enrich the records you will use.
- **Estimate worst case.** Worst-case credits equal the number of records you send to enrich. Log that number before every batch.
- **Store the ZoomInfo ID and last enriched date.** They drive matching and the 12-month gate.
- **Check the Usage endpoint.** Stop the job when remaining credits fall below a floor you set.
- **Enrich fewer fields.** It does not change credits per record, but it shrinks what can break in mapping.

For what credits cost, see our [ZoomInfo pricing guide](https://www.thequantumleap.business/blog/zoominfo-pricing-2026-solutions-partner-guide).

## Authentication and rate limit basics

The current ZoomInfo API uses OAuth 2.0. You create a Standard App in the ZoomInfo Developer Portal and choose a flow:

- **Client credentials** for server-to-server jobs. Your service exchanges a client ID and secret for an access token, and you pick an integration user that all calls are attributed to.
- **Authorization code with PKCE** when calls should act as a signed-in user.

Request only the scopes the job needs. Store the secret in HubSpot's secrets for custom code, or in your vault for middleware, never in a property. If an older build uses ZoomInfo's legacy API, which ZoomInfo now labels as legacy, plan its migration.

Rate limits are per tenant and depend on your package. ZoomInfo's rate limit page gives the Standard package as 25 requests per second, 54,000 per hour and 648,000 per day, all enforced together. A 429 response includes a Retry-After value, which can be minutes when an hourly window is exhausted, so respect it rather than retrying every second.

## What does custom cost to maintain?

The build is the cheap part. Plan for these ongoing jobs before you start:

- **Runtime changes.** HubSpot set November 17, 2026 as the date to move custom code actions off Node.js 16 and 20 to Node.js 24. Every runtime change means retesting.
- **API changes.** ZoomInfo has already announced rate limit header names that will be removed on January 1, 2027. Someone has to read changelogs.
- **Field changes.** A new HubSpot dropdown value or a renamed property breaks writes quietly.
- **Monitoring.** Failed runs, no-match rates and credit use need a weekly look, which belongs in your [integration health check](https://www.thequantumleap.business/blog/zoominfo-hubspot-integration-health-check).
- **An owner.** The most common failure we inherit is a build whose author left. Document the flow in plain English beside the code.

If the requirement can be met with the native settings plus [ZoomInfo Workflows and HubSpot workflows](https://www.thequantumleap.business/blog/zoominfo-workflows-vs-hubspot-workflows), that is almost always cheaper over two years. When it cannot, our [ZoomInfo consulting](https://www.thequantumleap.business/zoominfo-consulting) team scopes and builds the custom piece and hands it over documented.

## Conclusion

Native first, custom by exception. The native integration and Inbound Enrich handle standard companies and contacts well. The ZoomInfo API earns its keep when you need custom objects, rule-gated enrichment, hierarchy or data the integration does not write.

If you build, keep it small: gate every enrich call, store the ZoomInfo ID and date, respect rate limits, and give the build an owner. That is what separates a useful integration from a credit leak.

### Want an honest answer on native versus custom?

We run ZoomInfo and HubSpot together and will tell you if you do not need to build anything. [Book a free 30-minute fit check](https://meetings.hubspot.com/shawn-peterson/quantum-website).

## Frequently Asked Questions

### Do I need the ZoomInfo API to connect ZoomInfo to HubSpot?

No. ZoomInfo's platform integration, connected in the ZoomInfo Admin Portal, exports companies and contacts to HubSpot, and the ZoomInfo Inbound Enrich app on the HubSpot Marketplace enriches new records. The API is for requirements those two cannot meet.

### Does the ZoomInfo API use credits?

Search, lookup and find-similar calls are free. Enriching a company or contact uses one bulk data credit per new record, and enriching the same record again within 12 months does not use another credit.

### How does ZoomInfo API authentication work?

The current API uses OAuth 2.0. Server-to-server jobs use the client credentials flow with an integration user, and user-facing apps use the authorization code flow with PKCE.

### What are the ZoomInfo API rate limits?

They are set per tenant by package. ZoomInfo lists the Standard package at 25 requests per second, 54,000 per hour and 648,000 per day, and returns a Retry-After value on 429 responses.

### Can I call ZoomInfo from a HubSpot workflow?

Yes, with a custom code action, which needs Data Hub Professional or Enterprise. Each run must finish within 20 seconds and use no more than 128 MB of memory.

### Can ZoomInfo data go into HubSpot custom objects?

Yes, through a custom build that enriches via the ZoomInfo API and writes with HubSpot's API. Custom objects themselves need HubSpot Enterprise.

### Sources & References

- [ZoomInfo APIs: Credit Usage and Limits](https://docs.gtm.ai/docs/credit-usage-and-limits)
- [ZoomInfo APIs: Rate Limits](https://docs.gtm.ai/docs/rate-limits)
- [ZoomInfo APIs: Client Credentials Flow](https://docs.gtm.ai/docs/client-credentials-flow)
- [HubSpot: Custom code actions](https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions)
- [HubSpot Marketplace: ZoomInfo Inbound Enrich](https://ecosystem.hubspot.com/marketplace/listing/zoominfo-instant-enrich-by-zoominformation)

### Related Reading from Quantum

- [How to Connect ZoomInfo to HubSpot: Step-by-Step Setup](https://www.thequantumleap.business/blog/how-to-connect-zoominfo-to-hubspot)
- [ZoomInfo HubSpot Sync Errors: How to Find and Fix the Common Ones](https://www.thequantumleap.business/blog/zoominfo-hubspot-sync-errors)
- [Is Your HubSpot Data Ready for AI Agents?](https://www.thequantumleap.business/blog/hubspot-data-ready-for-ai-agents-checklist)

Ready to put any of this into practice? [See how ZoomInfo as a Service works →](https://www.thequantumleap.business/zoominfo-as-a-service)

### About the Author — Shawn Peterson

**CEO · Quantum Business Solutions · HubSpot Platinum Solutions Partner**

Shawn has spent 20+ years architecting revenue operations for B2B organizations across office equipment, MSP and IT services. Quantum is a HubSpot Platinum Solutions Partner and a ZoomInfo Diamond partner that builds HubSpot, runs outbound email and calling programs, and helps companies get found in search and AI answers. [Connect on LinkedIn →](https://www.linkedin.com/in/shawnpetersonquantum)

No call required

Do you need a custom ZoomInfo integration, or just better settings?

Tell us what you need ZoomInfo data to do in HubSpot and we will reply with whether native settings can do it or what a small custom build would look like. If native is enough, we will say that.

[View full post](https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Shawn Peterson"
  },
  "dateModified" : "2026-11-22T16:29:50.269Z",
  "datePublished" : "2026-11-22T16:29:50Z",
  "headline" : "ZoomInfo API and HubSpot: When a Custom Integration Beats the Native App",
  "image" : {
    "@type" : "ImageObject",
    "url" : "https://20682069.fs1.hubspotusercontent-na1.net/hubfs/20682069/blog/2026-11/zoominfo-api-hubspot-custom-integration.png"
  },
  "mainEntityOfPage" : "https://www.thequantumleap.business/blog/zoominfo-api-hubspot-custom-integration",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60.0,
      "url" : "https://20682069.fs1.hubspotusercontent-na1.net/hubfs/20682069/Untitled%20design%20(62)-1.png",
      "width" : 206.0
    },
    "name" : "Go-To-Market Blog"
  }
}
```