Your Workday org, always survey ready
Connect a Workday report once, and CultureMonkey keeps employees, teams, locations and reporting lines current twice a week for every survey.
Book a free, no-obligation product demo call with our experts.
How does the CultureMonkey Workday integration work?
CultureMonkey reads a custom report you publish from Workday and mirrors it into your employee list through a secure sync service. A first sync loads everyone, and after that the same report is re-read twice a week, so joiners, movers and leavers come across without anyone maintaining a spreadsheet.
Workday needs a report and a service account set up on its side, so the connection is provisioned with Customer Success rather than fully self-serve. Here is the shape of it:
- What you provideA Workday integration service-account username and password, and the web-service (RaaS) URL of a custom report listing your workers.
- How it authenticatesBasic Auth for that service account. There is no OAuth flow or app to install, and credentials are submitted through a secure link, never email or chat.
- What syncsEmployees, their teams, sub-teams, locations and business units, and the reporting lines between them.
- CadenceA first sync when you connect, then twice a week (currently Tuesday and Friday). Customer Success can trigger one on demand.
- Employee matchingExternal ID first, then email, so people already in CultureMonkey are updated rather than duplicated.
- LeaversMarked inactive, never deleted, once the report sends them as inactive. Their history and past responses stay intact.
What syncs from Workday, and how often
Type of integration
HRIS employee and org sync
Source
A Workday custom report (RaaS)
Sync cadence
Twice weekly, on demand via support
Employee matching
External ID, then work email
Accurate people data, straight from your system of record
Your employee list is what every survey, segment and manager dashboard rests on. Reading it from Workday on a schedule is what keeps the rest trustworthy.
Your Workday report sets the boundary
CultureMonkey sees exactly what your report returns, nothing more. You decide which workers and fields come across, then map each one to the attribute you cut engagement results by.
- Build a custom report of your workers and publish it as a web service; its URL is the connection's source.
- Field mappings link each Workday field to a CultureMonkey field. Sensible defaults apply, and you can review them.
- A department or location missing from the report will not appear, so the report is the first place to check when team-level results look incomplete.
Joiners, movers and leavers, without a spreadsheet
Each scheduled sync upserts your people, so your feedback audience reflects who works here this week.
- New workers in the report are created; existing ones are matched by external ID, then email, and updated.
- Map the date of separation to the active flag and job status, and leavers drop out of surveys once that date passes.
- Nobody is deleted. Departed employees are marked inactive and their history and responses are kept.
Reporting lines that resolve after every sync
Teams, locations and business units load first, then employees, then each person is linked to their manager, so manager dashboards show the right team.
- Include a manager identifier in your report and the hierarchy comes across with your people.
- A blank manager line usually means the report does not return that field, or it is not mapped.
- The same reporting lines build your org hierarchy: results for every manager's direct reports and everyone below them, up to 200 levels deep, refreshed each night after a change.
- Synced teams and locations only show results once they meet your anonymity threshold, a minimum group size of 5 by default, so finer org data never exposes an individual.
Credentials handled the way your IT team expects
The connection runs on a dedicated service account with only the access the report needs, which is how enterprise IT teams prefer integrations to work.
- A service account rather than a named person, so the sync survives role changes and stays easy to audit.
- Credentials are submitted through a secure link and stored against your account for the sync service alone.
- CultureMonkey will never ask for Workday credentials over email or chat.
The fields a Workday report can carry
CultureMonkey populates these from your report, depending on which fields it returns and how you map them. Seven are mandatory: first name, last name, email, employee ID, external ID, team and location.
| Category | Fields |
|---|---|
| Identity | First name, last name, email address, employee ID, external ID |
| Organization | Team, sub-team, location, business unit, designation |
| Reporting | Manager email, used to resolve the hierarchy |
| Employment | Date of joining, date of separation, employee type, role type, job status, active flag |
| Personal | Date of birth, gender, phone number, timezone, survey language |
Built for enterprise security, recognized for performance
Frequently asked questions
Can we set up the Workday connection ourselves?
What authentication does the Workday integration use?
How often does the Workday integration sync?
Does Workday sync teams and locations, or only people?
Will connecting Workday delete or overwrite our existing employees?
Why are some employees missing after a sync?
Why is someone who left still active?
We are moving off Workday Peakon. Does this integration replace it?
See the Workday sync running on your own org
Book a free, no-obligation product demo call with our experts.