Skip to content
CRM ⇄ Human resources

Clearbit to Greenhouse integration — real-time data sync

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

Flow Clearbit data into Greenhouse in real time — no exports, no schedulers, no custom scripts.

Clearbit 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 Clearbit — without exports, scripts, or schedulers.

Clearbit 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 Route and score inbound demo requests using Clearbit company size and industry data synced into the CRM.
  • 02 Refresh firmographic fields on existing accounts on a schedule so segmentation stays current.
  • 03 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
  • 04 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update stage, status, and custom fields in SQL while recruiters stay in Greenhouse.

Common sync patterns

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

Where Greenhouse tracks people the business also engages: contacts stay in sync

A person recorded in Greenhouse, such as a candidate or applicant, can create or update the matching contact in Clearbit, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

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

What you can sync between Clearbit and Greenhouse

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.

Clearbit objects Greenhouse objects How this pairing syncs
Companies Firmographic profiles looked up by domain and merged into account records. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Companies is specific to Clearbit and Applications to Greenhouse — each maps to any object or custom field on the other side.
Persons Individual profiles looked up by email and used to enrich contacts and leads. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Persons is specific to Clearbit and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Reveal matches IP-to-company resolutions used to identify anonymous website traffic. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Reveal matches is specific to Clearbit and Offers to Greenhouse — each maps to any object or custom field on the other side.
Name-to-domain lookups Company name resolution used to normalize account records before enrichment. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Name-to-domain lookups is specific to Clearbit and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Enrichment attributes The firmographic and technographic fields appended to destination records. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Enrichment attributes is specific to Clearbit and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.

How changes propagate between Clearbit and Greenhouse

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.

Clearbit Greenhouse Sub-second propagation

DetectionClearbit notifies Stacksync of record changes through webhook events. On-demand lookups.

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

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

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

Rate-limit considerations

  • Clearbit: Subject to plan-based API rate limits and lookup volumes.
  • 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.
What ships with Clearbit ⇄ Greenhouse

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Clearbit and Greenhouse connectors work

Clearbit

Integration surface
REST API (separate endpoints per product: Enrichment, Reveal)
Authentication
API key (bearer secret key)
Change detection
On-demand lookups; asynchronous enrichment results can be delivered via webhook callbacks
Capabilities
read · webhooks
Rate limits
Subject to plan-based API rate limits and lookup volumes

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
How it works

How to connect Clearbit to Greenhouse — 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 Clearbit and Greenhouse 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
    Clearbit connected
    Greenhouse connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Clearbit and Greenhouse 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 383 integrations available for Clearbit and Greenhouse.

Popular · 7 of 383
Coworkers laughing in front of a laptop in a casual office setting

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