Real-time
Two-way sync
Changes in Greenhouse or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Greenhouse to Kustomer integration — real-time, two-way sync
Keep Greenhouse and Kustomer 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 Greenhouse and Kustomer
Keep the people who own accounts in Kustomer 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.
Kustomer 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 Teams, Tags, Notes, Customers in Kustomer 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 Kustomer keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 02 Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance reporting
- 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
New team members provisioned when they are hired
When Greenhouse records a new hire, a matching user or owner is created in Kustomer, so a new rep can start working accounts without waiting on a manual setup ticket.
Ownership and territory follow the org chart
When a person changes team, manager, or region in Greenhouse, their accounts and territory assignments in Kustomer 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 Kustomer is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Greenhouse and Kustomer
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.
| Greenhouse objects | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Users Agent records map conversation ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Teams Team assignments support routing parity and reporting. | Applications is specific to Greenhouse and Teams to Kustomer — each maps to any object or custom field on the other side. | |
| Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. | Tags Labels on conversations and customers sync for categorization and analytics. | Jobs is specific to Greenhouse and Tags to Kustomer — each maps to any object or custom field on the other side. | |
| Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. | Notes Internal annotations carry context alongside synced conversations. | Offers is specific to Greenhouse and Notes to Kustomer — each maps to any object or custom field on the other side. | |
| Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Scorecards is specific to Greenhouse and Customers to Kustomer — each maps to any object or custom field on the other side. | |
| Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. | Conversations Support threads across channels sync outward for analytics and CRM context. | Scheduled Interviews is specific to Greenhouse and Conversations to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Greenhouse and Kustomer
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.
Greenhouse Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Greenhouse Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
DeliveryEach detected change is written to Greenhouse through its API, with automatic retries and rate-limit backoff.
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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Greenhouse ⇄ Kustomer
Connect Greenhouse and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Greenhouse or Kustomer 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 Greenhouse or Kustomer record.
Observability
Monitoring
Track your Greenhouse ⇄ Kustomer sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Greenhouse and Kustomer.
How the Greenhouse and Kustomer connectors work
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.
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Greenhouse to Kustomer — 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.
- 01
Connect your apps
Authenticate Greenhouse and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Greenhouse
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Greenhouse and Kustomer 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.
objects · Greenhouse ⇄ KustomerCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Greenhouse KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Greenhouse and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Kustomer: authenticate both systems, choose the objects to sync (such as Greenhouse's Users and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Greenhouse and Kustomer: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Greenhouse records a new hire, a matching user or owner is created in Kustomer, so a new rep can start working accounts without waiting on a manual setup ticket.
-
Greenhouse: 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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kustomer: Custom object types are called Klasses, and they are the standard mechanism for landing external data like orders and subscriptions where agents work. Greenhouse: Every write (POST, PATCH, DELETE) requires an On-Behalf-Of header carrying a valid Greenhouse user ID for the audit trail. Stacksync's field mapping accounts for these differences between Greenhouse and Kustomer without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Greenhouse and Kustomer records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Greenhouse and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Greenhouse–Kustomer integration in-house.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 418 integrations available for Greenhouse and Kustomer.
Popular · 7 of 418
-
Greenhouse ⇄ Freshsales -
Greenhouse ⇄ Freshworks CRM -
Greenhouse ⇄ Gladly -
Greenhouse ⇄ Gorgias -
Kustomer ⇄ Ukg Ready -
Kustomer ⇄ Success Factors -
Kustomer ⇄ Hibob
No integrations match .
