Skip to main content

​
What’s different about Workday

Most Tenzo ATS settings (stages, scoring, feedback, disposition, sync) work the same as other integrations. Workday adds a few things you must plan for: Deeper pages: Custom report for job fields, Workflow step cache, Custom fields (WSDL), Tenant namespace.

​
Prerequisites

  • Tenzo Admin and Workday Recruiting access to complete linking and tenant-side steps (per your org).
  • Ability to export the Recruiting WSDL from Workday when you set up custom field mapping.
Follow this exact order the first time through so workflow-step pickers, custom-field dropdowns, and candidate moves work without rework.
1

Connect Workday

In Admin → ATS Integrations, add or open the Workday integration and complete linking for your tenant.Full walkthrough: Connecting Workday to Tenzo.
2

Workflow steps (refresh cache, then configure)

Workday-specific: refresh the workflow step cache first, then set Start Workflow Steps and any per-transition workflow steps.
  • Eligibility: candidates match if they are in Start Stages or Start Workflow Steps (union, not intersection). If both are empty, Tenzo does not pull new applicants from Workday. Candidates already in Tenzo are unchanged.
  • Moves: if a transition has both a stage and a workflow step configured, the workflow step is used for that move.
Workflow step cache
3

Custom fields: WSDL import and tenant namespace

Workday-specific: import the Recruiting WSDL, set Workday tenant custom XML namespace when nested application paths apply, then complete Custom Field Mapping.Optional: if some job custom values only exist in reporting, configure a JSON custom report URL and credentials so Tenzo can merge those fields when loading jobs. Custom report for job fieldsCustom fields (WSDL) · Tenant namespace
4

Questionnaire permissions (application SMS consent)

If this tenant stores SMS consent on the application questionnaire, grant the Workday integration user Get access to Candidate Data: Questionnaires in the Recruiting functional area.If your tenant uses segmented questionnaire security, also grant the integration user access to the relevant Candidate Data: Initial Questionnaire and/or Candidate Data: Screen Questionnaire segment. Activate pending security policy changes after saving.Then in Admin → ATS Integrations → Configuration, turn on Enable application SMS consent and set the SMS consent Yes answer ID and SMS consent No answer ID (Workday Question_Multiple_Choice_Answer IDs, for example QUESTION_MULTIPLE_CHOICE_ANSWER-9-814 / QUESTION_MULTIPLE_CHOICE_ANSWER-9-815). Leave these off to keep candidate-level SMS consent.
5

Remaining ATS settings (stages, scoring, etc.)

Configure Candidate flow stages, scoring, feedback, disposition, activity feeds, and sync the way you would for any other integration—after workflow steps and custom fields are done, order no longer matters for Workday.

​
Before production

  • Workflow step cache refreshed with a recent run and non-zero count when you rely on steps.
  • WSDL import done; custom field pickers show the fields you expect.
  • Namespace set if you use nested application custom fields in mapping.
  • Questionnaire-response permission activated, and application SMS consent fields set, if this tenant uses questionnaire SMS consent.
  • Spot-check: one candidate’s eligibility, one move (stage or step), and one write to a mapped field.
Workday ATS (internal) — engineering notes and code pointers.