Personio
Read and write Personio persons, employments, absences and attendances, and read org units, cost centres, legal entities and workplaces through the v2 API.
Synchronise starters, org changes, leave and working time between Personio and payroll, identity, scheduling and finance systems.
Source actions
10
Destination actions
5
Data types
9
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
absence periods
- Create absence periodDestinationNot retried automatically
Records an absence (for example vacation) for a person.
- List absence periodsSourceIncremental
Absence periods, optionally for one person or type, or updated in a window.
absence types
- List absence typesSource
Absence types with category and unit (day or hour).
attendance periods
- Create attendance periodDestinationNot retried automatically
Records a work or break period for a person, optionally against a project.
- List attendance periodsSourceIncremental
Worked and break periods, optionally for one person, status or date window.
cost centers
- List cost centresSource
Cost centres configured in Personio.
employments
- List employmentsSourceIncremental
Employments of one person with position, status, org units, cost centres and termination.
- Update employmentDestinationDuplicate protected
Updates position, status, dates, working hours, supervisor, office, org units or cost centres.
legal entities
- List legal entitiesSource
Legal entities (employing companies) with country, status and address. Bank details are omitted.
org units
- List org unitsSource
Departments or teams with their parent hierarchy.
persons
- Create personDestinationNot retried automatically
Creates a person with an initial employment (position, dates, org units, supervisor).
- Get personSource
One person with custom attributes and employment IDs.
- List personsSourceIncremental
Persons (employees) with custom attributes, optionally changed after a timestamp.
- Update personDestinationDuplicate protected
Updates name, email, language or custom attributes. Omitted fields are unchanged.
workplaces
- List workplacesSource
Workplaces (offices) configured in Personio.
Authentication
Personio API client ID and secret (OAuth 2.0 client credentials)
Plans and access
API credentials are available on Personio plans with API access; attendance and absence APIs require the respective Personio modules. Each credential is limited to the scopes and attributes selected when it was generated (for example personio:persons:read, personio:absences:write).
Test environment
Personio provides demo or sandbox accounts to customers and partners on request.
Rate limits
The token endpoint allows 150 requests per minute; data endpoints are rate limited per credential and return HTTP 429 when exceeded.
Provider events
v2 webhooks for person, employment, absence and attendance events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Uses Personio API v2 only. The v1 custom-attribute metadata endpoint uses a different token flow and is not implemented; custom attribute IDs, labels and types are returned on each person instead.
- Compensations, salary bands, gender, bank details and legal entity bank accounts are never requested or returned.
- Absence periods can reveal sick leave through their absence type; restrict the credential's absence scopes if flows should not see them.
- Deleting persons, absences or attendances, document management and recruiting endpoints are not implemented.
- Creates have no idempotency key; uncertain writes are not repeated automatically.