The fastest way to kill adoption of a new hiring tool is to ask recruiters to re-key everything. If you run Workday Recruiting, your AI interviews should read requisitions from Workday and write results back, so recruiters stay in the system they know.
This guide explains how that works in principle, what to prepare, and how to roll it out without chaos. It also says plainly where our own Workday connector stands today.
Honest status first
Critical Hive's Workday connector works in sandbox mode (a built-in simulator we test against) and in live mode that is in early access: it has not yet been proven on a customer's live Workday tenant. Expect some per-tenant field mapping. For any other ATS today, use CSV import and export.
What flows in
- Requisitions: read from a custom report your Workday administrator publishes as JSON (Report-as-a-Service), so a role can be created from a requisition.
- Candidate events: when a candidate reaches a chosen stage, a signed webhook can invite them to the interview automatically, if you switch that on.
What flows back
- The interview outcome and score summary
- Links to the evidence report
- Status updates for the stage you choose
A person still decides. Writing back a score does not mean the score decides.
Preparation checklist
- Pick one requisition type to start with, not all of them.
- Decide the trigger stage, for example "Screen".
- Create an Integration System User with least privilege, and a report for requisitions.
- Agree what is written back and where recruiters will look for it.
- Test in the sandbox with fictional candidates first.
- Set retention and privacy notices before real candidates flow.
A safe rollout in four steps
- Run the connector in sandbox for a week and review the sync log.
- Pilot live on one requisition with automatic invitations off so recruiters invite manually.
- Turn automatic invitations on for that requisition once the data looks right.
- Expand to similar requisitions, one at a time.
Common pitfalls
- Mapping every custom field on day one.
- Letting automatic invitations loose before the privacy notice is updated.
- Forgetting that candidates who withdraw in Workday should not keep receiving reminders.
- Not training recruiters on the human-override step.
Beyond Workday
- CSV import brings candidates from any system in minutes, with a preview before sending.
- Microsoft Teams notifications post short cards to a channel when interviews are scored or a candidate asks for a person (early access).
- Calendars (Google and Microsoft) for interview booking (early access).
See the Workday integration page and the Teams page.
FAQ
Does the AI interview change my Workday data without approval?
Only what you configure. Start with read-only requisitions and manual invitations.
Can we use it with an ATS other than Workday?
Yes through CSV import and export today; other native connectors are on the roadmap.
Who maintains the integration?
Your Workday administrator maintains the report and credentials; we maintain the connector. Secrets are stored encrypted.
Next step
Ask for a walkthrough with your Workday admin in the room, or try the sandbox in a free pilot.