At a glance
Before you start
You need:- The workspace admin role in Pike.
- A Humaans admin who can see every person you want in Pike, including their job roles, time away and working patterns. An API access token never has more access than the person who creates it.
- An API access token. In Humaans, an admin opens the API access token settings, creates a token named Pike with read access to public and private data, and adds read access to compensations if you plan to use compensation sync. Choose no expiry, or note the expiry date so you can replace the token in time. Humaans shows the token only once.
- Pike time off types for the Humaans time away types you use. You map each type during setup. See Time off.
Connect Humaans
1
Open the integration
Go to Workspace settings → Integrations → Humaans and click Add
integration.
2
Enter your token
Paste the API access token and click Connect. Pike checks the token and
shows the Humaans company name.
3
Map time off types
Under Time off types, choose a Pike time off type for each Humaans time
away type. Pike suggests a mapping from the type names.
4
Choose what syncs
In the What syncs with Humaans card, turn Read on or off for each
entity, and choose whether to turn on Invite new employees.
5
Import
Click Import data. Departments import first, then people and their job
roles, then working patterns and time away.
What syncs
People
A job role with a future effective date applies in Pike from that date.
Working patterns
See Work schedule.
Time off
Default type mapping: vacation or annual leave to Vacation, sick to Sick, parental leave to Parental, time off in lieu to Time off in lieu, unpaid leave to Unpaid leave, and every other type to Vacation. Each type counts toward the member’s norm hours as set on the Pike type.
Compensation
Sync compensation to cost profiles is off by default. Only admins and finance users can turn it on. Pike reads base salary compensations only. Bonuses, commission and equity stay in Humaans.
See Cost profile.
Matching and duplicates
On the first import, Pike matches before it creates:- A person matches a Pike member with the same work email. A match links the two, and Humaans values replace the Pike values for the fields in the mapping.
- A department matches a Pike team with the same name. A job title matches a Pike position with the same name.
- Time away always imports as new time off. Time off already entered in Pike for the same member and dates stays, and the Humaans entry is listed in Sync issues as an overlap.
Which system wins
Edit Humaans-owned fields in Humaans. Pike shows them as read-only with the Humaans marker.
Sync schedule
Pike syncs Humaans every 3 hours. On the Enterprise plan, changes sync in real time. Import data, Sync now and Refresh on a member run straight away on every plan. See How sync works.Sync settings
While Humaans is connected, the What syncs with Humaans card is below the top button row on the integration page. Toggles save immediately.
New connections start with Read on for people, working patterns and time off, Invite new employees off, and compensation off.
How it works
Use it in Pike
Plan around approved leave
Open Members → Allocations to see each person’s capacity for the week. Approved Humaans time away shows on the day with its type, and the hours are already removed from capacity, so an over-allocated day stands out before the work is due. See Workspace capacity.Onboard a new hire
When a new person is added in Humaans, they appear in Pike with their team, position, manager and working pattern on the next sync. Turn on Invite new employees, or click Invite under Unmatched employees, and the person can log time on their first day.Offboard a leaver
When a person’s employment end date passes in Humaans, the member is deactivated in Pike. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from the end date.Measure utilization on contracted hours
A part-time working pattern in Humaans sets the member’s work schedule in Pike, so utilization for a four-day week is measured against four days, not five.Deletes and removed records
An integration never deletes Pike data. A person deleted in Humaans is marked Removed in Humaans on the member, stays in Pike with their history, and stops syncing. Time away deleted or canceled in Humaans after approval is removed from Pike capacity on the next sync, and the change appears in the member’s time off history.Troubleshooting
Limits
- Pike does not write to Humaans.
- Pending, declined or canceled time away does not sync.
- Compensation sync is off until an admin or finance user turns it on, and reads base salary only.
- The token syncs only the people and fields its creator can see.
Disconnect
Go to Workspace settings → Integrations → Humaans and click Disconnect. Syncing stops and every member, team, position, work schedule and time off entry stays in Pike with its history. Reconnecting the same Humaans company relinks the members. Revoke the token in Humaans if you no longer need it.Related
- How sync works: The schedule, real-time sync and sync issues.
- Working time: Work schedules, norm hours and capacity per week.
- Workspace capacity: How time off and contracts set available hours.
- Personio: Employees, absences and work schedules.
- HiBob: Employees, departments and time off policies.