HR · 12 pre-built actions
Personio integration with Nexus
Put Personio people data to work across your estate. Persons, attendances and document management actions run inside workflows that also reach identity, IT and collaboration tools.
Pre-built actions
What you can automate
12 pre-built Personio actions, grouped by what they work on.
12
PRE-BUILT ACTIONS
- 01Persons actions read employee records for onboarding and offboarding.
- 02Attendances actions bring time data into checks and reporting.
- 03Document Management actions file and retrieve employee documents as part of a process.
Workflow
How it fits into a Nexus workflow
Personio 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 Personio 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
Onboarding with document collection
A new person record starts identity provisioning and files signed documents back to Personio.
Attendance review
Attendance records outside policy are routed to the manager for confirmation.
Offboarding checklist
A leaver triggers access removal and an equipment return task, with the outcome recorded.
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 Personio
FAQ
Personio connector questions
- Which Personio actions are pre-built?
- Nexus includes 12 pre-built Personio actions across Document Management (4), Persons (5) and Attendances (3).
- Can Personio start a workflow?
- Runs that use Personio start from a webhook, a schedule or another trigger source. Personio steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Personio 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.
- Slack connector
Messages, users and channels.
- 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 Personio 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.