Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: CockroachDB and Greenhouse share the same people, positions, and org structure in real time.

Greenhouse is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. CockroachDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Departments and Offices, Candidates, Applications, Jobs in Greenhouse need to exist as queryable Indexes, Sequences, Changefeeds, Databases in CockroachDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Indexes, Sequences, Changefeeds, Databases in CockroachDB with Departments and Offices, Candidates, Applications, Jobs in Greenhouse field by field, in real time. You decide which system owns which fields — Greenhouse typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Use changefeeds to propagate row changes from a multi-region cluster into a warehouse or search index.
  • 02 Keep reference data consistent between CockroachDB and regional application databases.
  • 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

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Departments and Offices, Candidates, Applications, Jobs replicate into CockroachDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Greenhouse stay consistent in CockroachDB, so hierarchy-driven logic and permissions don't drift.

What you can sync between CockroachDB 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.

CockroachDB objects Greenhouse objects How this pairing syncs
Sequences ID generators that matter when writes originate from an external system. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Sequences is specific to CockroachDB and Applications to Greenhouse — each maps to any object or custom field on the other side.
Changefeeds Built-in CDC streams that emit row-level changes to external sinks. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Changefeeds is specific to CockroachDB and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Databases Logical containers a sync connects to, addressed like PostgreSQL databases. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Databases is specific to CockroachDB and Offers to Greenhouse — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to isolate synced tables from application tables. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Schemas is specific to CockroachDB and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Tables is specific to CockroachDB and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.
Views Read-only projections used as curated sync sources. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Views is specific to CockroachDB and Users to Greenhouse — each maps to any object or custom field on the other side.

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

CockroachDB Greenhouse Sub-second propagation

DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.

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

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

Rate-limit considerations

  • CockroachDB: No API rate limits in the SaaS sense; throughput is bounded by cluster capacity.
  • 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 CockroachDB ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the CockroachDB and Greenhouse connectors work

CockroachDB

Integration surface
SQL wire protocol (PostgreSQL-compatible)
Authentication
Database credentials with TLS; client certificates or SCRAM password auth
Change detection
CDC via changefeeds, which stream row-level changes; polling as a fallback
Capabilities
read · write · CDC
Rate limits
No API rate limits in the SaaS sense; throughput is bounded by cluster capacity

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 CockroachDB 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 CockroachDB 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
    CockroachDB connected
    Greenhouse connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

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 443 integrations available for CockroachDB and Greenhouse.

Popular · 7 of 443
All CockroachDB integrations All Greenhouse 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