HR · 66 pre-built actions
Workday integration with Nexus
People changes should move through systems with approval and evidence. Hires, moves and leavers touch HR, identity, IT and finance. Nexus puts the Workday step inside one governed run, so the downstream changes are validated, approved and recorded together.
Pre-built actions
What you can automate
66 pre-built Workday actions, grouped by what they work on.
66
PRE-BUILT ACTIONS
- 01Nexus includes 66 Workday actions.
- 02Capability groups: Employee (12), Payroll (15), Time Tracking (10), Benefits (13) and Recruitment (16).
Workflow
How it fits into a Nexus workflow
Workday is not listed among the current trigger sources. People workflows can start from a schedule, the webhook receiver, the HTTP poller or a ServiceNow request, and then read or update Workday inside the run.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Use the HTTP Request or SOAP Request node for Workday operations outside the pre-built actions.
02
Use Rules + Code for eligibility, effective dating and policy checks before anything is written.
03
Require approval before payroll or benefits changes that policy marks as sensitive.
Examples
Workflow examples
Joiner, mover, leaver coordination
A people change is validated, approved, and followed by identity and productivity steps in Okta and Microsoft 365.
Recruitment handoff
An accepted candidate moves toward onboarding with the downstream steps recorded in one run.
Scheduled consistency checks
A schedule compares employee data across HR and identity systems and routes differences to an owner.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Multi-system workflows
Use cases that include Workday
Integration patterns
Workday integration patterns
Dedicated patterns that pair Workday with another system in one governed run.
Industry use cases
Processes that use Workday
Public sector
Joiner, mover, leaver for public employees
Workforce changes become policy-checked identity changes, with collaboration set up and removed on time.
Defense & national security
Secure collaboration onboarding
New staff receive only the identity groups and collaboration spaces their role allows, after approval.
Financial services
Identity changes for regulated staff
Access changes for regulated roles carry a case record, approval and full evidence.
Healthcare
Healthcare employee onboarding
New staff get the identity access and collaboration their role needs, after approval.
Critical infrastructure
Identity access change for operations staff
Operations staff access follows their role, with changes approved and recorded.
Enterprise
Employee lifecycle automation
Joiners, movers and leavers are handled end to end with a case record and approval.
FAQ
Workday connector questions
- Which Workday areas are covered?
- Nexus includes 66 actions across Employee, Payroll, Time Tracking, Benefits and Recruitment.
- Can Workday start a workflow?
- Workday is not a listed trigger source. Use a schedule, webhook receiver, HTTP poller or another system event.
- Are payroll changes automatic?
- Only as your policy allows. Approval can be required before any payroll or benefits step.
Related reading
Continue from here
- Okta connector
Identity steps after a people change.
- Microsoft 365 connector
Productivity steps that follow.
- ServiceNow connector
Request context for people changes.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Workday fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.