Skip to main content
The Personio integration syncs employees, departments, positions, and absences into Pike, and sets each member’s weekly capacity from their Personio work schedule. Allocations and utilization use the hours people actually work.

Connect Personio

  1. Go to Workspace settings → Integrations → Personio.
  2. Click Add integration.
  3. Enter a Personio API client ID and secret.
Only workspace admins can connect or disconnect Personio.

Import data

On the integration page, click Import data. The stepper runs entities in dependency order, so Pike reads departments before the employees who belong to them. It skips entities whose Read toggle is off, names them, and links to sync settings.

What syncs

Time off

Approved absences from Personio create Pike time off of the type mapped to each absence type. Defaults: vacation to Vacation, sick to Sick, parental to Parental, and other types to Vacation. That removes those hours from capacity, so allocations and utilization stay correct. Pending or rejected requests do not sync.

Compensation

Sync compensation to cost profiles is off by default. Only admins and finance users can turn it on. When on, salary and pay period from Personio set the member’s cost profile, with the effective date from Personio.

Source of truth

Once a record is linked, Personio owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. Personio owns person fields.

Schedule

Pike reads employees from Personio every 24 hours and time off every hour. Import data and Refresh always run on demand.

Sync settings

While Personio is connected, the What syncs with Personio card sits under the top button row on the integration page. Each entity has a Read toggle (Personio to Pike). Toggles save immediately. New connections start with Read on for everything.

Synced records

Every synced record shows the Personio marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.

Sync issues

Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. The integration never deletes Pike data on its own. A record removed in Personio is marked “Removed in Personio” in Pike, never deleted.

Disconnect

Disconnecting Personio stops syncing and keeps all imported data. Linked records keep their history.

Permissions

Synced data respects Pike roles and private projects. A private project’s tasks never sync out to anyone who cannot see the project in Pike.

Limits

  • Pike does not write to Personio.
  • Pending or rejected absences do not sync.
  • Compensation sync is off until an admin or finance user turns it on.