Personio Personnel is the personnel-data API for Personio, a human-resources management platform for employee records and HR processes.

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

Personio Personnel

Personio Personnel is the personnel-data API for Personio, a human-resources management platform for employee records and HR processes.

Base URL: https://api.personio.de/v1
Auth: header:Authorization (pass your key via the apiKey input)

Operations

get_company_attendances — GET /company/attendances — This endpoint is responsible for fetching attendance data for the company employ
get_company_employees — GET /company/employees — List Employees
get_company_employees_employee_id — GET /company/employees/{employee_id} — Show employee by ID
get_company_employees_employee_id_profile_pictur — GET /company/employees/{employee_id}/profile-picture/{width} — Show employee profile picture
get_company_time_off_types — GET /company/time-off-types — Provides a list of available time-off types, for example 'Paid vacation', 'Paren
get_company_time_offs — GET /company/time-offs — This endpoint is responsible for fetching absence data for the company employees

Inputs

apiKey — your personio-personnel API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops

Example

operation: get_company_attendances
apiKey: <your key>

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
operation
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	DEPRECATED — bind an API Key credential to the task with `credentialName` instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
`operation`	string	yes	—	One of: get_company_attendances, get_company_employees, get_company_employees_employee_id, get_company_employees_employee_id_profile_pictur, get_company_time_off_types, get_company_time_offs
`employee_id`	string	no	—	Path parameter employee_id (required by some operations).
`width`	string	no	—	Path parameter width (required by some operations).
`query`	string	no	—	Optional query params as a JSON object string, e.g. {"limit": 10}.