Personio

Holiday approved in Personio, capacity adjusted in Linetrack.

When HR approves a fitter's holiday in Personio, those days drop out of assembly planning capacity shortly afterwards. Sick leave and training arrive the same way, and so do new employees. Linetrack does not need to know the reason for an absence: HR keeps it, planning sees the available days.
Personio website ↗

In short

Linetrack takes employee master data and absences from Personio through its REST API, matched by employee number. The sync is started by a Personio webhook via Zapier, Make or n8n, or alternatively by a fixed schedule; each run transfers the complete state of a period. In the privacy-compliant variant only the period of an absence arrives, without a reason such as sickness or holiday.

What is transferred

Maintained in Personio, calculated in Linetrack.

Employee master data

The sync creates new colleagues and updates existing ones. Records are matched by employee number, with the email address as fallback. Nothing is deleted.

PUT /resources/users/bulk

Absences with type

Holiday, sick leave, training and other types, half days included. Linetrack subtracts them from the available capacity, and planning sees why someone is away.

PUT /resources/absences/bulk

Absences without a reason

Only start and end, without type or description. Linetrack shows a neutral “Absence”. With this variant you go well prepared into the conversation with the works council and the data protection officer.

PUT /resources/absences/bulk/privacy-compliant

How the sync works

Three steps, then nobody maintains anything twice.

1

Create a key

An administrator creates an API key with the resources:write permission in Linetrack. The sync needs nothing more, and the key is valid for your company only.

2

Webhook from Personio

Personio reports new, changed and deleted absences by webhook to Zapier, Make or n8n, including the moment a request is approved. Alternatively the sync runs every night on a schedule.

3

Send the state to Linetrack

The workflow reads the absences of the period from Personio and sends the complete state to Linetrack. Whatever your planners entered directly in Linetrack stays untouched.

All workflows and the set-up in detail →

FAQ

Frequently asked questions

Any questions?

We work out with IT and HR which variant suits you.

How are employees matched between Personio and Linetrack?

By employee number. For master data, the email address serves as fallback where no employee number is maintained.

Can everyone in Linetrack see why an employee is absent?

Only if you want them to. With the privacy-compliant sync, Linetrack takes just the period and shows a neutral "Absence", without reason or description.

What happens to absences entered directly in Linetrack?

They stay as they are. The sync only replaces absences that came in through the interface.

Are employees who left in Personio deleted?

No. The master data sync creates and updates, but never deletes. Employees missing from a delivery stay unchanged in Linetrack.

Do we need programming skills?

No. Zapier, Make and n8n call Personio and Linetrack through ready-made building blocks or their HTTP module. You map the fields by click.