Skip to content
CRM ⇄ Human resources

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

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

Keep the people who own accounts in Clari in step with the workforce records in Greenhouse, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Clari runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Greenhouse. Greenhouse is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Audit Events, Forecast, Quota, Opportunities in Clari with Jobs, Offers, Scorecards, Scheduled Interviews in Greenhouse field by field, in real time, and in both directions. You decide which system owns which fields, so Greenhouse stays authoritative on roles and org structure while Clari keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
  • 02 Enrich Clari Account records with firmographic or billing data points through the ingest API in incremental mode.
  • 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

Deactivate access when someone leaves

When Greenhouse marks a worker as departed, the matching user in Clari is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

Where Greenhouse tracks people the business also engages: contacts stay in sync

A person recorded in Greenhouse, such as a candidate or applicant, can create or update the matching contact in Clari, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

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

Clari objects Greenhouse objects How this pairing syncs
Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Account field extensions is specific to Clari and Users to Greenhouse — each maps to any object or custom field on the other side.
Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Opportunity field extensions is specific to Clari and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side.
Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Audit Events is specific to Clari and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Forecast is specific to Clari and Applications to Greenhouse — each maps to any object or custom field on the other side.
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Quota is specific to Clari and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Opportunities is specific to Clari and Offers to Greenhouse — each maps to any object or custom field on the other side.

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

Clari Greenhouse Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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

Greenhouse Clari 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 written to Clari through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
  • 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 Clari ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Clari and Greenhouse connectors work

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.

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

    Choose tables

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

Clari 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 422 integrations available for Clari and Greenhouse.

Popular · 7 of 422
All Clari 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