Skip to content
Human resources ⇄ CRM

Hibob to ZoomInfo integration — real-time data sync

Keep Hibob and ZoomInfo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Hibob and ZoomInfo

Flow ZoomInfo data into Hibob in real time — no exports, no schedulers, no custom scripts.

ZoomInfo is a read-only source: Stacksync reads its data in real time and delivers it into Hibob, so Hibob always reflects the current state of ZoomInfo — without exports, scripts, or schedulers.

ZoomInfo runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Hibob. Hibob is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Common use cases

  • 01 Align CRM account hierarchies with ZoomInfo's corporate hierarchy data.
  • 02 Enrich CRM accounts and contacts on a schedule so firmographics, titles, and phone numbers stay current.
  • 03 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
  • 04 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.

Common sync patterns

New team members provisioned when they are hired

When Hibob records a new hire, a matching user or owner is created in ZoomInfo, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

When a person changes team, manager, or region in Hibob, their accounts and territory assignments in ZoomInfo update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

When Hibob marks a worker as departed, the matching user in ZoomInfo is flagged or deactivated, so former employees do not keep CRM access after their last day.

What you can sync between Hibob and ZoomInfo

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Hibob objects ZoomInfo objects How this pairing syncs
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Contact Profiles Person records with title, email, phone, and company linkage, used to enrich leads and contacts. Named lists is specific to Hibob and Contact Profiles to ZoomInfo — each maps to any object or custom field on the other side.
People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Intent Signals Company-level topic scores indicating in-market buying behavior. People (Employees) is specific to Hibob and Intent Signals to ZoomInfo — each maps to any object or custom field on the other side.
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Scoops Event-driven signals such as leadership changes, funding rounds, and new projects. Employment is specific to Hibob and Scoops to ZoomInfo — each maps to any object or custom field on the other side.
Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Technographics Technology install data per company, used for segmentation and territory planning. Work is specific to Hibob and Technographics to ZoomInfo — each maps to any object or custom field on the other side.
Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Company Hierarchies Parent and subsidiary linkage used to align CRM account hierarchies. Salaries is specific to Hibob and Company Hierarchies to ZoomInfo — each maps to any object or custom field on the other side.
Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Company Profiles Firmographic records covering industry, size, revenue, and location, matched against CRM accounts. Time off is specific to Hibob and Company Profiles to ZoomInfo — each maps to any object or custom field on the other side.

How changes propagate between Hibob and ZoomInfo

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Hibob ZoomInfo Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

DeliveryZoomInfo does not accept inbound record writes, so this direction carries requests rather than records: ZoomInfo's output flows back as field updates on the originating Hibob records.

ZoomInfo Hibob Interval-based propagation

DetectionStacksync polls ZoomInfo for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled re-enrichment and polling.

DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
  • ZoomInfo: Usage is metered by credits and contract-based limits rather than a single public rate limit.
What ships with Hibob ⇄ ZoomInfo

Connect Hibob and ZoomInfo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–ZoomInfo connection.

Real-time

Real-time sync

Changes in Hibob or ZoomInfo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Hibob or ZoomInfo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Hibob or ZoomInfo record.

Observability

Monitoring

Track your Hibob ⇄ ZoomInfo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Hibob and ZoomInfo.

How the Hibob and ZoomInfo connectors work

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob setup guide

ZoomInfo

Integration surface
REST API organized around search and enrich endpoints
Authentication
API credentials exchanged for a short-lived JWT
Change detection
Scheduled re-enrichment and polling; the platform is primarily a lookup and enrichment source, not an event stream
Capabilities
read
Rate limits
Usage is metered by credits and contract-based limits rather than a single public rate limit.
How it works

How to connect Hibob to ZoomInfo — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Hibob and ZoomInfo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Hibob connected
    ZoomInfo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and ZoomInfo objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Hibob ⇄ ZoomInfo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Hibob ZoomInfo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Hibob and ZoomInfo integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 436 integrations available for Hibob and ZoomInfo.

Popular · 8 of 436
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.