Skip to content
CRM ⇄ Human resources

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

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

Keep the people who own accounts in Chorusai 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.

Chorusai 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 Scorecards, Moments, Playlists, Engagements in Chorusai with Scorecards, Scheduled Interviews, Users, Departments and Offices 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 Chorusai keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Read the Deals associated with each conversation to attribute call activity to open opportunities in a BI model.
  • 02 Upload externally recorded dialer or web-conference audio into Chorus as Recordings so it gets transcribed and analyzed like native calls.
  • 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

Ownership and territory follow the org chart

When a person changes team, manager, or region in Greenhouse, their accounts and territory assignments in Chorusai update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

When Greenhouse marks a worker as departed, the matching user in Chorusai 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.

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

Chorusai objects Greenhouse objects How this pairing syncs
Users Chorus users with roles and team membership; read to map engagement owners and participants to CRM and warehouse identities. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Scorecards Call QA and coaching assessments with reviewer, recipient, and scores; read and exported for rep-performance reporting. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Recordings (Conversations) The recorded call with utterances, transcript, thumbnails, and metrics; read for analysis and uploaded or deleted through the API. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Recordings (Conversations) is specific to Chorusai and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Trackers AI keyword and topic trackers (pricing, competitors, next steps) surfaced within a conversation; read out as coaching and deal-risk signals. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Trackers is specific to Chorusai and Applications to Greenhouse — each maps to any object or custom field on the other side.
Deals CRM opportunity context attached to a conversation (account, deal, owner); read to attribute call activity to open pipeline. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Deals is specific to Chorusai and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Moments Timestamped highlight clips from a conversation; created via the API to capture key call snippets. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Moments is specific to Chorusai and Offers to Greenhouse — each maps to any object or custom field on the other side.

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

Chorusai Greenhouse Interval-based propagation

DetectionStacksync polls Chorusai for changes on an incremental schedule, reading only records changed since the previous pass. Polling the engagements endpoint on date_time and processing_state.

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

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

Rate-limit considerations

  • Chorusai: Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes.
  • 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 Chorusai ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Chorusai and Greenhouse connectors work

Chorusai

Integration surface
REST API (api-docs.chorus.ai)
Authentication
Per-user API token generated in Chorus Personal Settings, sent in the Authorization request header
Change detection
Polling the engagements endpoint on date_time and processing_state; no public change webhooks or CDC
Capabilities
read · write
Rate limits
Rate limits are not publicly documented; recording upload and analysis are asynchronous, so transcripts and trackers appear only after processing_state completes
Chorusai setup guide

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

    Choose tables

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

Chorusai 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 527 integrations available for Chorusai and Greenhouse.

Popular · 8 of 527
All Chorusai 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