Skip to content
Human resources

Connect Greenhouse to any app with two-way sync.

Two-way sync Greenhouse across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes
Setup guide: how Stacksync connects to Greenhouse

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
Object catalog

What Stacksync syncs in Greenhouse.

These objects sync between Greenhouse and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Greenhouse exposes them.

Candidates
Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines.
Applications
Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls.
Jobs
Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting.
Offers
Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire.
Scorecards
Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics.
Scheduled Interviews
Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs.
Users
Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write.
Departments and Offices
Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse.
API surface

How Stacksync connects to Greenhouse.

The connector runs on Greenhouse's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Greenhouse connector documentation
What ships with Greenhouse

Connect Greenhouse for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Greenhouse instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Greenhouse connector.

Greenhouse is the applicant tracking system (ATS) and system of record for recruiting, owned by Talent Acquisition and Recruiting Operations, usually with HRIS admins alongside. Candidates, Applications, Jobs, Offers, Scorecards, and interview data all live there, making it the source of truth for the hiring pipeline and funnel metrics. Downstream HRIS, analytics, and onboarding tools need to both read from and write back to it.

  • Recruiting operations
  • Talent acquisition / TA ops
  • HRIS administrators
  • People analytics
  • Data engineering

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

  2. Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.

  3. Push hired Applications and their Offers into an HRIS such as Workday or BambooHR to trigger onboarding and headcount records.

  4. Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.

  5. Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

  6. Two-way sync Candidates and Applications between Greenhouse and a Postgres database so recruiting-ops apps read and update stage, status, and custom fields in SQL while recruiters keep working in Greenhouse.

All Greenhouse integrations

Pick the system you need to keep in sync with Greenhouse. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 45

ERP · 38

Database · 50

Data warehouse · 29

Business productivity · 40

Accounting and finance · 17

How it works

Set up Greenhouse in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Greenhouse objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Greenhouse connector FAQ

What can I sync with the Greenhouse connector?

Greenhouse's core objects — Candidates, Applications, Jobs, Offers and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Greenhouse?

Via Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import), authenticated with 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. Changes are detected as follows — hMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Greenhouse connector two-way?

Yes. Changes made in Greenhouse propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Greenhouse integration take to set up?

Most Greenhouse integrations go live in minutes: authenticate Greenhouse and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Greenhouse data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Greenhouse data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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