Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: Couchbase 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. Couchbase is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Jobs, Offers, Scorecards, Scheduled Interviews in Greenhouse need to exist as queryable Global Secondary Indexes, XDCR replications, Full-text search indexes, Buckets in Couchbase 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 Global Secondary Indexes, XDCR replications, Full-text search indexes, Buckets in Couchbase with Jobs, Offers, Scorecards, Scheduled Interviews 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 Consolidate documents from multiple Couchbase clusters into a single analytical store.
  • 02 Write cleaned or enriched records from operational databases back into Couchbase collections that applications read.
  • 03 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.
  • 04 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.

Common sync patterns

Reporting and analytics on current data

Jobs, Offers, Scorecards, Scheduled Interviews replicate into Couchbase 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 Couchbase, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Couchbase write onto the matching record in Greenhouse where those fields are writable, keeping the people system enriched.

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

Couchbase objects Greenhouse objects How this pairing syncs
JSON Documents The core records; schemaless JSON keyed by document id, flattened or mapped to relational rows in syncs. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. JSON Documents is specific to Couchbase and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Global Secondary Indexes Indexes that make SQL++ query-based extraction efficient. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Global Secondary Indexes is specific to Couchbase and Applications to Greenhouse — each maps to any object or custom field on the other side.
XDCR replications Cluster-to-cluster replication streams, useful context when choosing a sync source cluster. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. XDCR replications is specific to Couchbase and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Full-text search indexes Search indexes over documents, relevant when syncing searchable content. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Full-text search indexes is specific to Couchbase and Offers to Greenhouse — each maps to any object or custom field on the other side.
Buckets Top-level data containers, roughly analogous to a database, that scope replication and memory quotas. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Buckets is specific to Couchbase and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Scopes Namespaces inside a bucket used to group collections, similar to schemas. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Scopes is specific to Couchbase and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.

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

Couchbase Greenhouse Sub-second propagation

DetectionChanges in Couchbase are captured at the source via change data capture — no polling loop against its API. Database Change Protocol (DCP) streams document mutations.

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

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

Rate-limit considerations

  • Couchbase: Throughput is bounded by cluster sizing rather than API rate limits.
  • 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 Couchbase ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Couchbase and Greenhouse connectors work

Couchbase

Integration surface
SQL++ (N1QL) query service, key-value SDK APIs, and REST management APIs
Authentication
Database credentials with role-based access control, typically over TLS
Change detection
Database Change Protocol (DCP) streams document mutations; SQL++ polling on document fields as an alternative
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by cluster sizing rather than API rate limits

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

    Choose tables

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

Couchbase 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 421 integrations available for Couchbase and Greenhouse.

Popular · 8 of 421
All Couchbase 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