HR · 13 pre-built actions
ADP Workforce Now integration with Nexus
Bring ADP workforce data into governed processes. Read and act on work assignments, job applicants and time records as steps in a workflow that also reaches identity, IT and finance systems.
Pre-built actions
What you can automate
13 pre-built ADP Workforce Now actions, grouped by what they work on.
13
PRE-BUILT ACTIONS
- 01Work Assignment actions support role and position changes that other systems depend on.
- 02Job Applicants actions bring recruiting context into onboarding preparation.
- 03Time actions make attendance data available to payroll checks and reporting.
Workflow
How it fits into a Nexus workflow
ADP Workforce Now steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
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
Call the ADP Workforce Now API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Role change to access review
A work assignment change is read from ADP and compared with access policy before Okta or Azure group changes run.
Applicant to onboarding preparation
An accepted applicant starts preparation tasks in ServiceNow or Jira, with a named owner for each.
Time exceptions to a manager
Time records outside policy are summarised and sent to the manager in Slack or Teams for a decision.
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.
Industry use cases
Processes that use ADP Workforce Now
FAQ
ADP Workforce Now connector questions
- Which ADP Workforce Now actions are pre-built?
- Nexus includes 13 pre-built ADP Workforce Now actions across Work Assignment (7), Job Applicants (3) and Time (3).
- Can ADP Workforce Now start a workflow?
- Runs that use ADP Workforce Now start from a webhook, a schedule or another trigger source. ADP Workforce Now steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the ADP Workforce Now API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Okta connector
Identity changes driven by workforce events.
- ServiceNow connector
Incidents, changes and CMDB.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how ADP Workforce Now 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.