Real-time
Two-way sync
Changes in Greenhouse or Workday instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Accounting and finance
Greenhouse to Workday integration — real-time, two-way sync
Keep Greenhouse and Workday 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 Workday
Keep the employee, department, and cost records that Workday and Greenhouse share consistent in real time, so the finance system and the people system stop drifting apart.
Workday runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Greenhouse runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.
Stacksync syncs Time Off and Absence, Payroll Results, Suppliers, Customers and Invoices in Workday with Scheduled Interviews, Users, Departments and Offices, Candidates in Greenhouse bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.
Common use cases
- 01 Push completed payroll results into a finance system or data warehouse each pay cycle.
- 02 Import journal entries from external billing or expense systems into Workday Financials.
- 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
- 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
Common sync patterns
One employee identity
A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.
Department and cost-center alignment
The org structure maintained in Greenhouse keeps the departments or cost centers in Workday current, so spend and headcount roll up the same way.
Status changes propagate
A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
What you can sync between Greenhouse and Workday
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 | Workday objects | How this pairing syncs | |
|---|---|---|---|
| Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Suppliers Workday Financials vendor records aligned with procurement tools. | Applications is specific to Greenhouse and Suppliers to Workday — 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. | Customers and Invoices Financials receivables objects synced for billing visibility where Workday Financials is used. | Jobs is specific to Greenhouse and Customers and Invoices to Workday — 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. | Journal Entries Accounting entries imported from external subledgers into Workday Financials. | Offers is specific to Greenhouse and Journal Entries to Workday — 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. | Custom Reports (RaaS) Tenant-defined reports exposed as web service endpoints, often the practical read surface for syncs. | Scorecards is specific to Greenhouse and Custom Reports (RaaS) to Workday — 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. | Workers The central HCM record covering employment, job, and personal data; the anchor of most syncs. | Scheduled Interviews is specific to Greenhouse and Workers to Workday — each maps to any object or custom field on the other side. | |
| Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Organizations Supervisory and company hierarchies read to drive routing and reporting in other systems. | Users is specific to Greenhouse and Organizations to Workday — each maps to any object or custom field on the other side. |
How changes propagate between Greenhouse and Workday
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 Workday 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 Workday through its API, with automatic retries and rate-limit backoff.
Workday Greenhouse Interval-based propagation
DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.
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.
What ships with Greenhouse ⇄ Workday
Connect Greenhouse and Workday for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Workday connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Greenhouse or Workday 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 Workday record.
Observability
Monitoring
Track your Greenhouse ⇄ Workday 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 Workday.
How the Greenhouse and Workday 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.
Workday
- Integration surface
- SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
- Authentication
- OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
- Change detection
- Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
- Capabilities
- read · write
How it works
How to connect Greenhouse to Workday — 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 Workday 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
Workday
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Greenhouse and Workday 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 ⇄ WorkdayCustomers 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 WorkdayCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Greenhouse and Workday integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Workday: authenticate both systems, choose the objects to sync (such as Greenhouse's Applications and Jobs), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Workday side: Time Off and Absence, Payroll Results, Suppliers, Customers and Invoices, plus custom fields where Workday 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 Workday: One employee identity; Department and cost-center alignment; Status changes propagate. A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.
-
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. Workday: SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports. Authentication: OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP. Stacksync manages authentication, retries, and rate limits on both sides.
-
Workday: Workday data is effective-dated: records carry validity dates, and reads can be scoped to an as-of moment, which shapes how syncs interpret changes. Greenhouse: Pagination is Link-header (RFC-5988) based with per_page between 1 and 500 (default 100). Stacksync's field mapping accounts for these differences between Greenhouse and Workday without custom code.
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 495 integrations available for Greenhouse and Workday.
Popular · 8 of 495
-
Greenhouse ⇄ Zuora -
Greenhouse ⇄ Adyen -
Greenhouse ⇄ Logisense -
Greenhouse ⇄ Bill -
Workday ⇄ Lever -
Workday ⇄ Namely -
Workday ⇄ Paylocity -
Workday ⇄ Ukg Ready
No integrations match .
