Workday
Purpose
Ingests Workday employee directory data (people, titles, emails, supervisory organizations, and reports-to relationships) to enrich identity and ownership context across your graph.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into SubImage's managed vault. See Secrets for details.
Required Fields
| Field | Secret? | Description |
|---|---|---|
workday_api_url |
No | Workday RaaS report endpoint URL, e.g. https://wd5-services.myworkday.com/ccx/service/customreport2/company/report/directory |
workday_api_login |
No | Workday API username, e.g. api_user@company |
workday_api_password |
Yes | Password for the Workday API user |
Setup Steps
- Ask your Workday administrator for a RaaS (Report as a Service) report that returns the employee directory as JSON. See Report Fields for what the report should contain.
- Obtain read-only API credentials for the report (Integration System User recommended). Ensure the URL uses HTTPS.
- In SubImage, fill in:
workday_api_url— the RaaS endpoint URLworkday_api_login— the API usernameworkday_api_password— the password (or its AWS Secret ARN)
- Save the module.
Uses HTTP Basic authentication.
Report Fields
The only field each report entry must contain is:
| Field | Description |
|---|---|
Employee_ID |
Unique employee identifier, used as the person's ID |
The following fields are optional, but each one unlocks additional properties or relationships in the graph:
| Field | Effect when present |
|---|---|
Name |
Sets the employee's display name |
Email_-_Work |
Sets the work email used to match the person against identities from other modules |
Supervisory_Organization |
Creates the organization node and attaches the employee to it |
Worker_s_Manager_group |
Creates the reports-to relationship, using the Manager_ID of its first entry |
Other optional fields (businessTitle, Worker_Type, location, Cost_Center, Team, Company, …) are ingested as properties when present.