At a glance
Before you start
You need:- The workspace admin role in Pike.
- A Factorial user with the administrator role in the company you want to connect. Pike asks for read access to employees, teams, legal entities, contracts, time off and compensations.
- To connect with an API key instead of signing in, a Factorial API key. In Factorial, open Settings, select API keys in the Advanced section, name the key Pike, and click Get my API key. Factorial shows the key only once.
- Pike time off types for the Factorial leave types you use. You map each leave type during setup. See Time off.
Connect Factorial
1
Open the integration
Go to Workspace settings → Integrations → Factorial and click Add
integration.
2
Authorize Pike
Click Sign in with Factorial, sign in as a Factorial administrator and
approve the access Pike asks for. To use an API key, click Use an API
key, paste the key and click Connect. Pike shows the Factorial company
name.
3
Choose legal entities
Under Legal entities, choose which Factorial legal entities sync.
Employees of other legal entities do not import.
4
Map leave types
Under Time off types, choose a Pike time off type for each Factorial
leave type. Pike suggests a mapping from the type names.
5
Choose what syncs
In the What syncs with Factorial card, turn Read on or off for each
entity, and choose whether to turn on Invite new employees.
6
Import
Click Import data. Teams import first, then employees, then contracts,
then leaves.
What syncs
Employees
Contracts
Weekly capacity is spread over Monday to Friday. To give a part-time member a different pattern, such as four days a week, set the work schedule in Pike. Pike uses that schedule as long as its weekly total matches the Factorial contract.
Leaves
Default type mapping: vacation to Vacation, sick to Sick, parental to Parental, time off in lieu to Time off in lieu, unpaid 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.
See Cost profile.
Matching and duplicates
On the first import, Pike matches before it creates:- An employee matches a Pike member with the same email. A match links the two, and Factorial values replace the Pike values for the fields in the mapping.
- A team matches a Pike team with the same name. A job title matches a Pike position with the same name.
- Leaves always import as new time off. Time off already entered in Pike for the same member and dates stays, and the Factorial leave is listed in Sync issues as an overlap.
Which system wins
Edit Factorial-owned fields in Factorial. Pike shows them as read-only with the Factorial marker.
Sync schedule
Pike syncs Factorial 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 Factorial is connected, the What syncs with Factorial card is below the top button row on the integration page. Toggles save immediately.
New connections start with Read on for employees, contracts and leaves, every legal entity selected, 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 Factorial leaves show on the day with their 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 employee is added in Factorial, they appear in Pike with their teams, position and weekly capacity 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 an employee is terminated in Factorial, the member is deactivated in Pike from the termination date. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from that date.Update capacity after a contract change
When HR changes someone’s working hours in Factorial, the new contract version sets their weekly capacity from its effective date. Utilization for earlier weeks still uses the old hours.Deletes and removed records
An integration never deletes Pike data. An employee deleted in Factorial is marked Removed in Factorial on the member, stays in Pike with their history, and stops syncing. A leave deleted or rejected in Factorial 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 Factorial.
- Pending or rejected leaves do not sync.
- Factorial attendance shifts do not import. Members log their time in Pike.
- Compensation sync is off until an admin or finance user turns it on, and reads base salary only.
- One Pike workspace connects to one Factorial company.
Disconnect
Go to Workspace settings → Integrations → Factorial and click Disconnect. Syncing stops and every member, team, position, capacity setting and time off entry stays in Pike with its history. Reconnecting the same Factorial company relinks the members.Related
- How sync works: The schedule, real-time sync and sync issues.
- Time off: Time off types and how they count toward capacity.
- Workspace capacity: How time off and contracts set available hours.
- Personio: Employees, absences and work schedules.
- HiBob: Employees, departments and time off policies.