Skip to content
Human resources ⇄ Data warehouse

Greenhouse to Starburst Enterprise integration — real-time, two-way sync

Keep Greenhouse and Starburst Enterprise 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 Starburst Enterprise

Land the people and organization records from Greenhouse in Starburst Enterprise 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 Starburst Enterprise next to everything else the company measures.

Stacksync syncs Departments and Offices, Candidates, Applications, Jobs from Greenhouse into tables in Starburst Enterprise continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Starburst Enterprise, 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 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 02 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 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

Write-back of computed values

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

HR data in the warehouse, minus the pipeline

People and organization records from Greenhouse arrive in Starburst Enterprise as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

Analysts combine Greenhouse's workforce records with finance, product, or operational data already in Starburst Enterprise for reporting the HR system cannot produce on its own.

What you can sync between Greenhouse and Starburst Enterprise

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 Starburst Enterprise objects How this pairing syncs
Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Scheduled Interviews is specific to Greenhouse and Catalogs to Starburst Enterprise — 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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Users is specific to Greenhouse and Schemas to Starburst Enterprise — 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. Tables Queryable relations; writes pass through to sources whose connectors support them. Departments and Offices is specific to Greenhouse and Tables to Starburst Enterprise — 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. Views Engine-level SQL views used to shape federated data before syncing it out. Candidates is specific to Greenhouse and Views to Starburst Enterprise — 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. Materialized views Precomputed results that make repeated sync reads cheaper. Applications is specific to Greenhouse and Materialized views to Starburst Enterprise — 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. Columns Typed per the Trino type system, mapped from each source's native types. Jobs is specific to Greenhouse and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Starburst Enterprise

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 Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Greenhouse Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Greenhouse ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

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

    Choose tables

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

Greenhouse and Starburst Enterprise 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 Starburst Enterprise.

Popular · 6 of 436
All Greenhouse integrations All Starburst Enterprise 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