Skip to content
Human resources ⇄ Data warehouse

Greenhouse to MotherDuck integration — real-time, two-way sync

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

Land the people and organization records from Greenhouse in MotherDuck as live tables for workforce reporting, without extract jobs, and write computed results back where Greenhouse can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Greenhouse is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in MotherDuck next to everything else the company measures.

Stacksync syncs Departments and Offices, Candidates, Applications, Jobs from Greenhouse into tables in MotherDuck continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in MotherDuck, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Greenhouse where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Share curated, synced datasets with other teams through read-only database shares
  • 02 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 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

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

Queryable history for planning and audit

A continuously synced copy in MotherDuck gives you a durable, queryable record of how Greenhouse's records change over time, for headcount planning and audit questions.

Write-back of computed values

Segments, rollups, or risk flags computed in MotherDuck sync back onto the matching records in Greenhouse, where the HR team sees them in the system they already use.

What you can sync between Greenhouse and MotherDuck

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 MotherDuck objects How this pairing syncs
Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Schemas Namespaces within a database used to organize synced tables. Offers is specific to Greenhouse and Schemas to MotherDuck — 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. Tables The main landing target for synced records and source for analysis. Scorecards is specific to Greenhouse and Tables to MotherDuck — 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. Views Modeled projections used as outbound sync sources. Scheduled Interviews is specific to Greenhouse and Views to MotherDuck — each maps to any object or custom field on the other side.
Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Database Shares Read-only copies of a database shared with other users or teams. Users is specific to Greenhouse and Database Shares to MotherDuck — each maps to any object or custom field on the other side.
Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Departments and Offices is specific to Greenhouse and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side.
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Candidates is specific to Greenhouse and Databases to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and MotherDuck

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 MotherDuck 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 /.

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

MotherDuck Greenhouse Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. 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.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with Greenhouse ⇄ MotherDuck

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Greenhouse ⇄ MotherDuck 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 MotherDuck.

How the Greenhouse and MotherDuck 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

MotherDuck

Integration surface
SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
Authentication
Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide
How it works

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

    Choose tables

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

Greenhouse and MotherDuck 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 449 integrations available for Greenhouse and MotherDuck.

Popular · 8 of 449
All Greenhouse integrations All MotherDuck 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