Resources · Zapier integration

Personio Zapier integrationAutomate Personio with Zapier.

The Personio Zapier integration gives you 12 triggers, 7 actions and 5 searches to move HR events out of Personio and back into it. Five triggers are instant, it works on the free plan, and this page shows what each step costs and where it breaks.

See the 24 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Personio Zapier integration actually does

Zapier links Personio to the other tools your HR team uses, without code. You build a Zap, an automation made of one starting event and the steps that follow it every time that event happens. On the Personio side, that means 24 visible operations: things Personio can report, things Zapier can write into it, and lookups.

Three results people build first. A filed onboarding pack: when New Employment Created fires, Upload File to Employee drops the handbook or the contract template into the new hire's documents. A recruiting pipeline that feeds itself: a form or a job board on another tool runs Create Applicant, so nobody retypes names into Personio. An absence calendar kept in step: New Absence pushes each new time-off into a shared calendar or a team channel, so managers stop asking who is out.

The detail that changes everything on a free plan: five Personio triggers are instant (Personio itself tells Zapier, so the 15-minute wait of the free plan does not touch them). Those are the two attendance triggers and the three employment triggers. The other seven, from New Absence to New Open Position, are checked on a timer. If timing matters, start your Zap on an instant one.

What Zapier does not do for Personio: it never deletes anything (no delete action exists), it cannot touch compensation records except to notice them, and it only sees what happens after your Zap is switched on. Old absences or past hires stay where they are. If you prefer building on another platform, the same app also has a Personio Make integration, and the Make vs Zapier comparison sits next to it.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

Zap
Your automation on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it and starts on its own.
Action
What the Zap does after it starts: the step that creates, updates or uploads something in an app for you.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so it skips the wait.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can use what it found.
Connection
Your Personio account linked to Zapier once, then reused by every step of every Zap that touches Personio.
Cost

What a Personio Zap really costs

Personio is not a premium app on Zapier: it runs on the free plan. The bill is counted in tasks, and only completed actions count.

  • Triggernever counted
  • Successful action1 task each
  • Failed actionnot counted
  • Free plan100 tasks a month, two-step Zaps only
  • Personionot premium, works on the free plan

The trigger never costs a task, and neither do the checks Zapier runs on a polling trigger, however often they happen. Each successful action counts once, so a Zap with three actions uses three times more than a one-action Zap. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter, a search step or a second action and it becomes a multi-step Zap, which needs a paid plan.

Connect

Connect Personio to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. You need a Personio account first, plus access to any records you do not own but want the Zap to read or change.

  2. 02

    Find Personio and confirm

    Type Personio in the search box of the dialog, pick it, then click Add connection. A new tab opens on the Personio side so you can sign in with the account the Zap should act as.

  3. 03

    Grant access

    Sign in to Personio in that tab and give Zapier access to the account. The connection now shows up in your list, and every Zap step that uses Personio can pick it without asking again.

First Zap

Your first Personio Zap: onboarding documents on autopilot

GoalEach new employment in Personio gets the welcome handbook filed in the employee's documents, without anyone opening the profile.

  1. 01

    Build: pick the starting event

    Create a Zap, choose Personio as the trigger app and New Employment Created as the event. Pick your Personio connection. This trigger is instant, so the plan interval does not apply.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of your account, so you map the next steps on a real employment instead of an empty example.

  3. 03

    Add a search to get the person

    Add Find Person and feed it a value the trigger returned. It hands the following step a confirmed Personio person. This search makes the Zap multi-step, so a paid plan is needed.

  4. 04

    Add the upload action

    Add Upload File to Employee. Map the employee ID from the search, set the Category ID of your onboarding category, give the file as a link, and type a file name that ends with its extension.

  5. 05

    Test, then publish

    Test each step and read what came back in Personio. When the file lands in the right category, publish the Zap to switch it on. From then on, each new employment runs it once.

Triggers

Personio triggers on Zapier

12 events start a Zap when something happens in Personio, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Absence

Polling trigger

In Zapier“Triggers when a new absence is created.”

Starts your Zap on each new absence created in Personio. Good for mirroring absences into a shared calendar or a channel your team actually reads.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a team lead wants the morning stand-up board to show who is away without opening Personio.
Watch out
on the free plan an absence can take up to a full interval to show up, so do not use it for same-minute alerts.
2

New Attendance (Instant)

Instant trigger

In Zapier“Triggers instantly when a new attendance period is created.”

Reacts to every new attendance period recorded in Personio, the worked time HR tracks per employee. It is one of the five instant Personio triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a shift manager wants a payroll sheet or a project tracker to receive each logged period without waiting for an export.
Watch out
busy teams log many periods, and each one runs the Zap, so watch your task count.
3

Updated Attendance (Instant)

Instant trigger

In Zapier“Triggers instantly when an attendance period is updated.”

Fires when someone corrects an attendance period that already exists in Personio. It lets the copies of that period elsewhere follow the correction.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your timesheet spreadsheet must reflect the corrected hours, not only the first entry.
Watch out
if your Zap also runs Update Attendance on Personio, it can set itself off again in a loop.
4

New Candidate

Polling trigger

In Zapier“Triggers when a new Candidate is created.”

Picks up every candidate newly created in Personio recruiting, whichever channel they applied through. A clean way to tell hiring managers that a fresh profile is waiting.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a recruiter wants each candidate posted in the hiring channel of the department concerned.
Watch out
a bulk import of old applicants can arrive as one large batch, which Zapier may hold back.
5

New Employee Compensation Record (Starts Today)

Polling trigger

In Zapier“Triggers when a new Employee Compensation Record is effective today.”

Fires on the day a new compensation record becomes effective, not on the day someone types it in. That timing is what makes it useful for payroll and finance follow-ups.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
finance needs a note in its own tracker on the day a raise actually applies.
Watch out
no Zapier action edits compensation, so this trigger only informs other tools.
6

New Document

Polling trigger

In Zapier“Triggers when a new document is created for the specified Owner”

Watches the documents of one specific owner in Personio and starts the Zap each time a new one is added there. It does not scan the whole account.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a signed contract added to a manager's profile should be copied to the legal team's archive.
Watch out
the Owner ID field is required, so one Zap follows one owner, and covering several people means several Zaps.
7

New Employee

Polling trigger

In Zapier“Triggers when a new employee is created.”

Starts on each employee newly created in Personio. This is the classic entry point for onboarding work in the tools Personio does not manage itself.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
IT wants a ticket for each new hire, so the laptop and accounts are ready on day one.
Watch out
if timing is tight, New Employment Created is instant and covers the same moment of the hiring.
8

Employee Updated

Polling trigger

In Zapier“Triggers when an employee is updated.”

Reacts when an existing employee record changes in Personio. It keeps a second tool, a directory or an org chart, aligned with what HR edits.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your internal directory must show new job titles or teams without manual copying.
Watch out
a Zap that runs Update Employee on the same person can retrigger itself and burn through tasks.
9

New Employment Created

Instant trigger

In Zapier“Triggers when one or more Employment details of a Person are created”

Fires when employment details of a person are created in Personio, which in practice marks the start of someone's contract with you. Several details created together can arrive in one go.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
onboarding steps in other tools must start the same day the contract is entered.
Watch out
it only covers employments created after the Zap is on, never the ones already in place.
10

Employment Terminated

Instant trigger

In Zapier“Triggers when an existing employment is terminated.”

Starts the Zap when an existing employment ends in Personio. It is the natural hook for offboarding, the part of HR people most often forget to automate.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
IT must revoke access and recover equipment on the day HR records a departure.
Watch out
a termination entered by mistake still runs the Zap, so keep a human check before anything irreversible.
11

Employment Updated

Instant trigger

In Zapier“Triggers when one or more Employment details of a Person are updated”

Picks up changes to the employment details of a person in Personio. Several changes saved together can come through at once.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a department change should update permissions or distribution lists in your other tools.
Watch out
a filter helps keep only the changes you care about, but it makes the Zap multi-step.
12

New Open Position

Polling trigger

In Zapier“Triggers when a new open position is created.”

Notices each new open position created in Personio. It turns a decision taken in HR into an announcement or a task elsewhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
marketing wants each new opening queued for the careers page or social posts.
Watch out
positions opened before the Zap was switched on are never picked up, so publish those by hand.
Actions

Personio actions on Zapier

Personio gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Applicant

Action

In Zapier“Creates a new applicant.”

Adds a new applicant to Personio recruiting, attached to a job position. Ideal when people apply through a form or a site outside Personio.

When to use it
your careers landing page collects names and you want them in the hiring pipeline directly.
Watch out
Job Position, First Name and Last Name are required, and the position must already exist.
2

Create Absence

Action

In Zapier“Creates a new absence.”

Records a time-off period for an employee in Personio, from another tool where the request started.

When to use it
leave is approved in a ticketing tool and must land in Personio without a second entry.
Watch out
six fields are required, including the absence type and whether the first and last days are half-days.
3

Create Attendance

Action

In Zapier“Creates a new attendance.”

Writes a new attendance period into Personio for one employee. It saves staff from logging hours twice when they already track them elsewhere.

When to use it
time tracked in a project tool should become attendance in Personio.
Watch out
the Employee field is required, so the Zap needs a way to know the Personio ID.
4

Create Employee

Action

In Zapier“Creates a new employee.”

Opens a new employee record in Personio. Useful when the hiring decision is captured in another system first and HR should not retype it.

When to use it
a signed offer in your e-signature tool should create the employee in Personio.
Watch out
pair it with Find Employee in find-or-create mode to avoid duplicates.
5

Update Attendance

Action

In Zapier“Updates an existing attendance.”

Changes an attendance period that already exists in Personio. It is how a correction made in another tool reaches the official record.

When to use it
a manager fixes hours in a shared sheet and Personio must follow.
Watch out
the Attendance ID is required, so put Find Attendance before it.
6

Update Employee

Action

In Zapier“Updates an existing employee.”

Edits an existing employee record in Personio with values coming from another step. It keeps Personio the reference when changes start elsewhere.

When to use it
a new team assignment decided in your planning tool should reach the employee profile.
Watch out
do not combine it with Employee Updated on the same record, or the Zap loops.
7

Upload File to Employee

Action

In Zapier“Uploads a new file to an employee.”

Files a document in an employee's profile, either a file from an earlier step or a link to one, inside the category you choose.

When to use it
signed contracts or certificates should be stored in Personio without anyone downloading and re-uploading them.
Watch out
the file name must include its extension, such as .pdf, and the Category ID is required.
Searches

Personio searches on Zapier

5 search steps look for data that already exists in Personio, so a later step can use it.

A search step finds a record already in Personio and hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not what you expected.

1

Find Absence

SearchFind or create

In Zapier“Finds an absence by employee ID.”

Looks up absences of one employee, by their employee ID. The editor also shows Find or Create Absence: same search, with the creation box ticked.

When to use it
before booking a meeting, check whether the person already has time off recorded.
Watch out
the Employee ID is required, so add Find Employee first if you only have an email.
2

Find Attendance

SearchFind or create

In Zapier“Finds a attendance by employee ID.”

Returns attendance periods of an employee. An option includes pending periods next to confirmed ones. Find or Create Attendance is this same search with creation turned on.

When to use it
fetch the period you need to correct before running Update Attendance.
Watch out
without Include Pending, entries awaiting approval stay invisible to the Zap.
3

Find Document

Search

In Zapier“Finds a document by owner ID”

Retrieves documents that belong to one owner in Personio, so a later step can send or archive them.

When to use it
on a termination, gather the departing person's documents for the exit file.
Watch out
the Owner ID is required; the search never looks across the whole account.
4

Find Employee

SearchFind or create

In Zapier“Finds a employee based on email.”

Finds an employee from an email address, the bridge between tools that know people by email and Personio, which knows them by ID. Find or Create Employee is this search with creation ticked.

When to use it
a form sends an email and you need the matching Personio record.
Watch out
a typo in the email returns nothing and stops the Zap by default.
5

Find Person

Search

In Zapier“Finds a person by their Personio ID, name, last name and email, optionally including their absence information.”

Looks up a person by Personio ID, first name, last name or email, and can bring their absence periods along with the record.

When to use it
a chat message names a colleague and you need their profile plus time off in one step.
Watch out
searching by name alone can match several people, so set the multiple-results rule.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap carries on without the value.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it asks for the fields needed to create the missing item instead of stopping.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass all matches on to the next steps at once.
When it breaks

When a Personio Zap breaks

Zapier lists no help article and no rate limit specific to Personio. The failures you will meet are the general ones, and each has a clear cause.

Most of them come from timing and loops, not from Personio itself. If a Zap misbehaves, the Zapier troubleshooting page covers the general method.

  • No catching up on the past

    A Zap only reacts to what happens after you switch it on. Employees, absences or candidates already in Personio are never picked up; moving them is a separate job.

  • The Zap that feeds itself

    Employee Updated plus Update Employee on the same record, or the attendance pair, makes the Zap set itself off again and again, and the task count drains fast.

  • Bulk imports held back

    After a migration or a mass import into Personio, a trigger can suddenly return a huge batch. Zapier's flood protection may then hold it instead of running everything.

  • Same item, only once

    On a polling trigger, Zapier remembers what it has already seen, so the same absence or candidate does not start the Zap twice, even after a later check.
Need help

Need help automating Personio with Zapier?

A person reads every message.

FAQ

Personio and Zapier: frequent questions

01Is the Personio Zapier integration free?
Yes, Personio is not a premium app, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. Once you add a filter, a search such as Find Employee or a second action, the Zap becomes multi-step and needs a paid plan. Most onboarding scenarios with a lookup therefore start on a paid plan, while a simple New Absence to calendar Zap fits on the free one.
02How many tasks does a Personio Zap use?
One task per action that completes successfully, and nothing else. The trigger is free, and so are the checks Zapier runs on polling triggers like New Employee or New Candidate. A Zap that runs Upload File to Employee for each new employment uses one task per new hire, and an action that fails is not counted. Watch triggers that fire often, such as the attendance ones: every logged period runs the Zap, and each run spends its tasks.
03Does Personio send events to Zapier in real time?
For five triggers, yes in practice: New Attendance (Instant), Updated Attendance (Instant), New Employment Created, Employment Terminated and Employment Updated are instant, so Personio reports them to Zapier itself and the Zap starts right away on any plan. The seven others are polling triggers. Zapier checks them on a timer that depends on the plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Instant or polling is set by the app and cannot be changed from the editor.
04What is required to connect Personio to Zapier?
A Personio account, plus read or write access on any records you do not own and want the Zap to touch. On the Zapier side, open the Apps page, click + Add connection, search Personio, confirm with Add connection, then sign in to Personio in the tab that opens and grant access. The connection is then reused by every Personio step. Before building, also check that the job positions and document categories your actions need already exist.
05Why does New Document only see some documents?
Because it watches one owner at a time. The Owner ID field is required on the New Document trigger and on the Find Document search, so a Zap follows the documents of a single person, not the whole account. To cover a team, build one Zap per owner, or start from an instant trigger such as New Employment Created and use Find Document for the person concerned. Upload File to Employee has the same logic: one employee and one category per run.
06What if the Personio operation that fits is not on Zapier?
Then the Personio integration on Zapier does not cover it, and no setting in the editor will add it. The 24 visible operations are the full list: there is no delete action, and compensation records can only be watched, not edited. Options are to change the scenario so it uses an existing operation, such as Update Employee instead of a dedicated field action, or to check whether another automation platform covers that step for Personio.
07Zapier, Make or n8n for Personio?
It depends on your criteria, not on a ranking. On Zapier, Personio offers 12 triggers, five of them instant, 7 actions and 5 searches, works on the free plan, and every step is set up from a menu without code. Look at the operations you need first, then at how the bill is counted: on Zapier it is one task per successful action. If your scenario needs many lookups or filters, check how the other platform counts those steps before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations