Real-time
Two-way sync
Changes in Greenhouse or Monday instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Greenhouse to Monday integration — real-time, two-way sync
Keep Greenhouse and Monday 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 Monday
Keep the people, teams, and status that Monday and Greenhouse share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Monday keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Greenhouse is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Workspaces, Boards, Items, Subitems in Monday with Scheduled Interviews, Users, Departments and Offices, Candidates in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in Monday within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Monday captures details of its own, such as a corrected contact or a login identity, those can flow back to Greenhouse in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Mirror monday.com Boards, Groups, and Subitems into a warehouse for cross-project reporting on status and timelines without CSV exports.
- 02 Push support tickets or orders from an operational database into monday.com Items, then read status Column values back when work completes.
- 03 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
- 04 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.
Common sync patterns
Onboarding: access ready on day one
A new hire recorded in Greenhouse creates the matching user in Monday with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Greenhouse, the matching account in Monday is deactivated or flagged, so departures do not leave open access behind.
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
What you can sync between Greenhouse and Monday
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 | Monday 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 Account members referenced by people columns; read to resolve owner and assignee IDs to names and emails. | 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. | Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. | Applications is specific to Greenhouse and Boards to Monday — 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. | Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. | Jobs is specific to Greenhouse and Items to Monday — 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. | Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. | Offers is specific to Greenhouse and Subitems to Monday — 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. | Column values Typed fields (status, date, people, numbers, connect-boards); polymorphic JSON usually written together via change_multiple_column_values. | Scorecards is specific to Greenhouse and Column values to Monday — 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. | Groups Named sections that group items inside a board; synced as a grouping attribute or category field on the row. | Scheduled Interviews is specific to Greenhouse and Groups to Monday — each maps to any object or custom field on the other side. |
How changes propagate between Greenhouse and Monday
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 Monday 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 Monday through its API, with automatic retries and rate-limit backoff.
Monday Greenhouse Sub-second propagation
DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.
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.
- Monday: Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window.
What ships with Greenhouse ⇄ Monday
Connect Greenhouse and Monday for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Monday connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Greenhouse or Monday 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 Monday record.
Observability
Monitoring
Track your Greenhouse ⇄ Monday 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 Monday.
How the Greenhouse and Monday 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.
Monday
- Integration surface
- GraphQL API (single endpoint, api.monday.com/v2)
- Authentication
- OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header
- Change detection
- Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field
- Capabilities
- read · write · webhooks
- Rate limits
- Complexity-budget limits: a single query caps at 5M complexity points and ~10M points/min per user token (1M on trial/free) over a sliding 60s window
How it works
How to connect Greenhouse to Monday — 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 Monday 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
Monday
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Greenhouse and Monday 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 ⇄ MondayCustomers 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 MondayCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Greenhouse and Monday integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Monday: 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.
-
Yes — Stacksync ships production-grade connectors for both Greenhouse and Monday. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Greenhouse: HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters. On Monday: Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events; polling falls back to the item updated_at field. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Monday side: Workspaces, Boards, Items, Subitems, plus custom fields where Monday exposes them. On the Greenhouse side: Scheduled Interviews, Users, Departments and Offices, Candidates. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Greenhouse and Monday: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Greenhouse creates the matching user in Monday with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
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 511 integrations available for Greenhouse and Monday.
Popular · 8 of 511
-
Greenhouse ⇄ Klaviyo -
Greenhouse ⇄ Lemlist -
Greenhouse ⇄ Lusha -
Greenhouse ⇄ Microsoft 365 -
Monday ⇄ BambooHR -
Monday ⇄ Success Factors -
Monday ⇄ Hibob -
Monday ⇄ Ceridian Dayforce
No integrations match .
