# Workday integrations

*5 integrations*

**In short:** Integrating Workday means feeding its effective-dated business processes rather than writing fields: hires, job changes and terminations come in from a local HRIS or an applicant tracking system, and completed events go out to ServiceNow. What breaks is treating Workday like a table: wrong effective dates, events that skip approval routing, duplicate workers from weak ID matching, and foundation data that does not exist yet.

## What connects to Workday

Workday is the global HCM in groups that span countries and legal entities: the system of record for supervisory organizations, positions, compensation and worker history. Around it sit systems closer to local or operational work.

A DACH subsidiary runs [Personio](https://seamless.engineering/integrations/personio-workday/) or [BambooHR](https://seamless.engineering/integrations/bamboohr-workday/) for day-to-day HR and feeds hires, changes and absences up. An applicant tracking system like [Greenhouse](https://seamless.engineering/integrations/greenhouse-workday/) opens the Hire or Pre-Hire process when a candidate accepts, and receives approved requisitions back. Where part of the group runs SAP SuccessFactors Employee Central, the two are kept aligned with one of them as system of record. Downstream, [ServiceNow](https://seamless.engineering/integrations/workday-servicenow/) reads completed business processes to update users, managers and onboarding and offboarding cases.

## Where Workday integrations break

- **Business processes, not field writes.** A hire, a promotion or a termination is a Hire, Change Job or Terminate business process that may route for approval. Writing fields onto a worker bypasses approvals and breaks the audit trail, and a submitted event is not a completed one.
- **Effective dating.** Every change is valid from a date and history is kept. A sync that stamps changes with today's date rewrites compensation and headcount history, and future-dated changes have to be held before downstream systems apply them.
- **Worker identity.** Workday Employee IDs and WIDs share nothing with the source system's IDs. Matching on name or email creates a duplicate worker on the first surname change or rehire, so every pipeline holds a stable cross-reference.
- **Foundation data first.** A hire fails if its supervisory organization, position or cost center does not exist yet. Under Position Management it needs an open position, so reference data is mapped and synced before the people.
- **SOAP, RaaS and throughput.** Workday Web Services and RaaS reports have their own paging, concurrency limits and version lifecycle. Loads run in batches with backoff, and one rejected worker must not roll back the rest.

## All Workday integrations

### HR ↔ Payroll

- [Personio ↔ Workday](https://seamless.engineering/integrations/personio-workday/): Personio Workday integration
- [BambooHR ↔ Workday](https://seamless.engineering/integrations/bamboohr-workday/): BambooHR Workday integration
- [Workday ↔ ServiceNow](https://seamless.engineering/integrations/workday-servicenow/): Workday ServiceNow integration
- [SAP SuccessFactors ↔ Workday](https://seamless.engineering/integrations/successfactors-workday/): SAP SuccessFactors Workday integration

### Recruiting ↔ HRIS

- [Greenhouse ↔ Workday](https://seamless.engineering/integrations/greenhouse-workday/): Greenhouse Workday integration

## Request a scoping call

Connecting Workday to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.

- Email: hello@seamless.engineering
- Contact form: https://seamless.engineering/#contact