Greenhouse + Workday Integration
Greenhouse Workday integration syncs hired candidates into Workday worker records automatically — zero manual re-entry, no code.
Eliminate manual re-entry — hired candidates become Workday workers automatically
Cut time-to-productivity with IT provisioning triggered on day-one hire events
Keep recruiting and headcount planning in sync with bidirectional position data
Today
Hired in Greenhouse, invisible in Workday until someone re-enters the data
- Recruiting teams close a hire in Greenhouse and the celebration ends there — because nothing happens in Workday until HR manually re-enters the same candidate data: name, email, start date, department, compensation, and manager.
- This handoff takes hours, introduces errors, delays IT provisioning, and means new hires arrive to missing accounts, incomplete onboarding tasks, and frustrated managers.
- Headcount approvals live in Workday while open roles live in Greenhouse with no automated bridge between them — so requisitions lag approvals by days.
With Koodisi
Automated Greenhouse ↔ Workday Sync with Koodisi
- Koodisi automates the hire-to-onboard handoff so every candidate marked as Hired in Greenhouse automatically becomes a Worker in Workday — with the right department, manager, compensation, and start date.
- Offer data maps to Workday fields without manual translation.
- In the other direction, headcount positions approved in Workday automatically open as requisitions in Greenhouse.
- Recruiting and HR stay aligned on one source of truth without copying data between tabs.
The sync
What moves, in both directions
Greenhouse and Workday stay in step because the sync runs both ways.
Create Worker records on hire, sync offer data (compensation, start date, job title), trigger pre-boarding tasks, and close Workday positions when filled.
Push approved headcount positions as open jobs, sync department and org structure updates, and send hiring manager data to Greenhouse job records.
Automating this handoff compresses time-to-productivity for new hires, eliminates data entry errors between ATS and HRMS, and gives HR a clean audit trail from offer to onboarded Worker.
Use cases
What teams automate with this integration
The work that moves between Greenhouse and Workday today, and what Koodisi takes over.
Hired candidate in Greenhouse triggers Workday Worker creation
- When an application moves to Hired status in Greenhouse, Koodisi reads the candidate's profile and offer details — name, email, job title, department, manager, start date, and compensation — and creates a new Worker record in Workday.
- The record is created with the correct cost centre, position, and supervisory organisation so payroll, benefits, and IT provisioning can all trigger from the same event.
- HR does not touch the data; the Workday record is ready before the candidate's first day.
- Business outcome: faster onboarding, fewer errors in compensation setup, and no delayed IT access for incoming employees.
Offer acceptance triggers Workday pre-boarding tasks
- When a Greenhouse offer is accepted, Koodisi triggers a pre-boarding workflow in Workday that creates the pre-hire profile, initiates background check tasks, and routes onboarding paperwork to the new hire's email.
- The flow maps offer data — start date, role, manager — to the correct Workday onboarding template.
- IT provisioning tickets open automatically in the ITSM system, and the hiring manager receives a confirmation in Slack.
- Outcome: new hires complete paperwork before day one, IT has lead time to provision accounts, and HR avoids chasing last-minute forms during the first week.
Approved Workday headcount position creates Greenhouse job
- When a headcount position is approved in Workday — via the standard requisition approval workflow — Koodisi creates the corresponding open job in Greenhouse with the correct department, location, hiring manager, and job description template.
- Recruiters see the approved role immediately without waiting for a manual handoff from Finance or HR.
- Workday approval details (cost centre, level, compensation band) carry forward to the Greenhouse job record so there is no ambiguity about what was approved.
- Outcome: recruiting begins faster after headcount approval, fewer mis-scoped requisitions, and a clear audit trail from approved position to filled hire.
Greenhouse stage changes trigger Workday and team notifications
- As a candidate progresses through key Greenhouse pipeline stages — interview scheduled, offer extended, background check passed — Koodisi triggers corresponding actions in Workday and Slack.
- Offer extended events create a pending Worker record in Workday so HR can start compensation review in parallel.
- Background check completion updates the Workday pre-hire record status.
- Hiring managers receive Slack DMs at each stage so they can prepare without logging into Greenhouse.
- This keeps all stakeholders informed, reduces time spent on status requests, and means Workday data is always one step ahead of the official start date.
The workflow
What this looks like when it runs
- Koodisi connects Greenhouse and Workday using its no-code REST Client for both platforms.
- Greenhouse hire events — application status changes, offer acceptances, stage progressions — trigger Koodisi workflows that read candidate and offer data, map it to Workday's Worker, Position, and Onboarding APIs, and write the records with full field validation.
- For the reverse direction, Workday approval events trigger Koodisi to read position data and create or update Greenhouse jobs.
- Every sync is logged with a timestamped audit trail, retries handle transient API errors automatically, and exception alerts surface any mismatches that require human review before data is committed to either system.
Greenhouse Hired → Workday Worker onboarding
- 1Candidate application status changes to Hired in Greenhouse — Koodisi detects the event via REST Client
- 2Koodisi reads candidate profile, offer data, and hiring manager from Greenhouse
- 3Koodisi maps fields to Workday Worker schema and creates the Worker record with correct org, position, and start date
- 4Workday confirmation triggers IT provisioning alert and day-one checklist for the hiring manager
Workday approved position → Greenhouse open job
- 1Headcount requisition is approved in Workday — Koodisi detects the status change
- 2Koodisi reads position details: department, level, compensation band, hiring manager, and location
- 3Koodisi creates an open Job in Greenhouse with correct fields and assigns the hiring manager
- 4Recruiter receives a Slack notification that the role is open and ready to source
Governance
Automated, but still under control
Every run is authorised, recorded, and observable — the part that decides whether automation survives an audit.
Scoped permissions
Role-based access decides who can publish or run the Greenhouse and Workday workflows, and who can only watch them.
Every run recorded
Each execution writes an audit trail — what triggered it, what changed, and what the downstream system returned.
Credentials in Key Vault
Greenhouse and Workday credentials are stored and retrieved from Key Vault, never pasted into workflow steps.
Traced end to end
OpenTelemetry logs, metrics, and traces show where a run slowed down or failed, rather than reporting one aggregate status.
Routing rules stay readable
Which records sync, and which need approval first, live in a decision table your team can review and change without editing the workflow.
Sensitive fields masked
Personal and commercial values can be masked in logs so an operational record does not become a copy of your customer database.
Ship integrations faster. Operate them without chaos.
Less time on auth, retries, and deployment scripts. More time on the integrations your customers are asking for.
Contact Sales