Skip to content
Database ⇄ Human resources

Azure Cosmos DB to Greenhouse integration — real-time, two-way sync

Keep Azure Cosmos DB 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 Azure Cosmos DB and Greenhouse

Put your workforce data where your apps can reach it: Azure Cosmos DB 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. Azure Cosmos DB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Scorecards, Scheduled Interviews, Users, Departments and Offices in Greenhouse need to exist as queryable Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB 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 Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB with Scorecards, Scheduled Interviews, Users, Departments and Offices 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 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 02 Consolidate documents from multiple containers into a single reporting store.
  • 03 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.
  • 04 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.

Common sync patterns

Computed and operational fields flow back

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

Mirror people records into the database

Records maintained in Greenhouse land as queryable Change feed entries, Stored procedures and triggers, Databases, Containers in Azure Cosmos DB, so internal apps and dashboards read live data instead of a periodic export.

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.

What you can sync between Azure Cosmos DB 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.

Azure Cosmos DB objects Greenhouse objects How this pairing syncs
Containers The unit of partitioning and throughput; each container maps to a synced collection. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Containers is specific to Azure Cosmos DB and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Items (JSON documents) is specific to Azure Cosmos DB and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Partition keys is specific to Azure Cosmos DB and Users to Greenhouse — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Change feed entries is specific to Azure Cosmos DB and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side.
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Stored procedures and triggers is specific to Azure Cosmos DB and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Databases is specific to Azure Cosmos DB and Applications to Greenhouse — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB 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.

Azure Cosmos DB Greenhouse Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

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

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.
What ships with Azure Cosmos DB ⇄ Greenhouse

Connect Azure Cosmos DB and Greenhouse for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Greenhouse.

How the Azure Cosmos DB and Greenhouse connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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

    Choose tables

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

Azure Cosmos DB 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 438 integrations available for Azure Cosmos DB and Greenhouse.

Popular · 7 of 438
All Azure Cosmos DB 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