Introduction
Integration overview
The Deeper Signals platform integrates with Workday in two surfaces. They are independent of each other — you can deploy one or both — but they share the same OAuth credentials and security group.
| Surface | What it does | Workday APIs used |
|---|---|---|
| ATS (Recruiting) | Detects candidates that have been moved to a Deeper Signals assessment in Workday, sends them the assessment, and writes the results, the per-dimension scores, and the PDF report back to Workday. | SOAP Recruiting v45.2 — Get_Assess_Candidate, Get_Candidates, Get_Job_Requisitions, Get_Organizations, Assess_Candidate, Put_Candidate_Attachment; REST /api/customObject/v2. |
| HRIS (Workers) | Synchronises your worker directory into Deeper Signals on a recurring schedule, builds the manager / org hierarchy used for access control, and writes assessment results back to the worker record after a hire. | SOAP Human_Resources v45.2 — Get_Workers; SOAP Staffing v45.2 — Put_Worker_Document; REST /api/customObject/v2. |
Authentication is OAuth 2.0 with a non-expiring refresh token, configured once on a single API Client for Integrations.
Choosing ATS only, HRIS only, or both
| If your goal is... | Configure |
|---|---|
| Send Deeper Signals assessments from Workday to candidates and see the results on the Job Application. | Part 1 (Shared) + Part 2 (ATS). |
| Sync your existing employees into Deeper Signals so managers can run team analytics, plus push results to the worker record after a hire. | Part 1 (Shared) + Part 3 (HRIS). |
| End-to-end candidate-to-hire journey with continuous worker sync — recommended for most clients. | Part 1 + Part 2 + Part 3. |
:::info ATS-only deployments need fewer Workday permissions
The three options above do not require the same access. An ATS-only deployment is confined to the Recruiting candidate record: it needs no worker-data domains, no supervisory-organisation access, and neither the Staffing nor Personal Data OAuth scope. Those grants back code paths that check for an HRIS integration and never execute without one.
When scoping an ATS-only deployment, add only §1.3.1 and the six OAuth scopes not marked HRIS only in §1.6. The trade-off is that recruiters and hiring managers are not resolved to Deeper Signals users automatically, so campaigns are created without an auto-assigned owner. :::
Prerequisites
Before starting, identify:
- A Workday administrator who can run security and integration tasks on your tenant.
- A target Workday environment (a sandbox / impl tenant first, then production). The integration is configured per-tenant.
- A Deeper Signals admin account on your tenant — used in Parts 2.2, 4, and 5 to copy campaign IDs and configure the integration in Settings → Integrations.
:::info End-to-end self-service
The entire setup is self-service. Workday credentials, custom-object aliases, field mappings, and campaign IDs are all entered directly in the Deeper Signals admin app — nothing needs to be sent, emailed, or shared with Deeper Signals support. Part 4 — Configuration checklist consolidates the values; Part 5 walks through entering them. :::