Skip to content
Human resources ⇄ CRM

Greenhouse to ZoomInfo integration — real-time data sync

Keep Greenhouse 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 Greenhouse and ZoomInfo

Flow ZoomInfo data into Greenhouse 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 Greenhouse, so Greenhouse 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 Greenhouse. Greenhouse 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 Enrich CRM accounts and contacts on a schedule so firmographics, titles, and phone numbers stay current.
  • 02 Sync intent signals into the CRM or warehouse to trigger outbound plays on in-market accounts.
  • 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
  • 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

Common sync patterns

New team members provisioned when they are hired

When Greenhouse 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 Greenhouse, their accounts and territory assignments in ZoomInfo update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

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

Greenhouse objects ZoomInfo objects How this pairing syncs
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Company Profiles Firmographic records covering industry, size, revenue, and location, matched against CRM accounts. Candidates is specific to Greenhouse and Company Profiles to ZoomInfo — each maps to any object or custom field on the other side.
Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Contact Profiles Person records with title, email, phone, and company linkage, used to enrich leads and contacts. Applications is specific to Greenhouse and Contact Profiles to ZoomInfo — each maps to any object or custom field on the other side.
Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Intent Signals Company-level topic scores indicating in-market buying behavior. Jobs is specific to Greenhouse and Intent Signals to ZoomInfo — each maps to any object or custom field on the other side.
Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Scoops Event-driven signals such as leadership changes, funding rounds, and new projects. Offers is specific to Greenhouse and Scoops to ZoomInfo — each maps to any object or custom field on the other side.
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Technographics Technology install data per company, used for segmentation and territory planning. Scorecards is specific to Greenhouse and Technographics to ZoomInfo — each maps to any object or custom field on the other side.
Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Company Hierarchies Parent and subsidiary linkage used to align CRM account hierarchies. Scheduled Interviews is specific to Greenhouse and Company Hierarchies to ZoomInfo — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse 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.

Greenhouse ZoomInfo Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

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

ZoomInfo Greenhouse 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 Greenhouse through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
  • ZoomInfo: Usage is metered by credits and contract-based limits rather than a single public rate limit.
What ships with Greenhouse ⇄ ZoomInfo

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Greenhouse 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 Greenhouse or ZoomInfo record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Greenhouse and ZoomInfo connectors work

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse 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 Greenhouse 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 Greenhouse 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
    Greenhouse connected
    ZoomInfo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Greenhouse 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 · Greenhouse ⇄ 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
    Greenhouse ZoomInfo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

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

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

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

Popular · 8 of 436
All Greenhouse integrations All ZoomInfo integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own