At a glance
Before you start
You need:- The workspace admin role in Pike.
- Your Lucca address, for example
northlight.ilucca.net. - A Lucca API key. A Lucca administrator creates it under Settings → API keys with Generate API key, and gives it read access to the directory (users), organization structure (departments and legal entities) and Timmi Absences (leaves and leave accounts). To send time, the key also needs write access to Timmi Timesheet time entries. The key syncs only the users and data its rights allow.
- Pike time off types for the Lucca leave accounts you use, such as Congés payés or RTT. You map each leave account during setup. See Time off.
Connect Lucca
1
Open the integration
Go to Workspace settings → Integrations → Lucca and click Add
integration.
2
Enter your credentials
Enter your Lucca address and the API key, then click Connect. Pike
checks the key and shows your Lucca company name.
3
Choose legal entities
Under Legal entities, choose which Lucca legal entities sync. Users of
other legal entities do not import.
4
Map leave accounts
Under Time off types, choose a Pike time off type for each Lucca leave
account. Pike suggests a mapping from the account names.
5
Choose what syncs
In the What syncs with Lucca card, turn Read and Send on or off
for each entity, and choose whether to turn on Invite new employees.
6
Import
Click Import data. Departments import first, then users, then work
cycles, then leaves.
What syncs
Users
Work cycles
The weekly total of the work cycle sets the member’s capacity per week. See Working time.
Leaves
Default type mapping: vacation and Congés payés to Vacation, sick to Sick, parental to Parental, RTT and time off in lieu to Time off in lieu, unpaid to Unpaid leave, and every other account to Vacation. Each type counts toward the member’s norm hours as set on the Pike type.
Send time to Timmi Timesheet
Send time to Timmi Timesheet is off by default. When on, closing a pay period in Pike sends each linked member’s approved time for the period to Timmi Timesheet as one time entry per day. Only approved entries count.
Pike sends the entries as imported time, so employees edit their hours in Pike and not in Timmi Timesheet. The timesheet then follows your Timmi Timesheet approval workflow in Lucca. A correction to a period already sent replaces that period’s entries the next time the period is sent.
Matching and duplicates
On the first import, Pike matches before it creates:- A user matches a Pike member with the same email. A match links the two, and Lucca 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.
- Leaves always import as new time off. Time off already entered in Pike for the same member and dates stays, and the Lucca leave is listed in Sync issues as an overlap.
Which system wins
Edit Lucca-owned fields in Lucca. Pike shows them as read-only with the Lucca marker.
Sync schedule
Pike syncs Lucca every 3 hours. On the Enterprise plan, changes sync in real time. Closing a pay period sends time to Timmi Timesheet straight away on every plan, as do Import data, Sync now and Refresh. See How sync works.Sync settings
While Lucca is connected, the What syncs with Lucca card is below the top button row on the integration page. Toggles save immediately.
New connections start with Read on for users, work cycles and leaves, every legal entity selected, Invite new employees off, and Send time to Timmi Timesheet 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 Lucca leaves show on the day with their type, and a half-day leave removes only its half of the day, so an over-allocated day stands out before the work is due. See Workspace capacity.Onboard a new hire
When a new user is added to the Lucca directory, they appear in Pike with their team, position and work schedule 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 user’s contract end date passes in Lucca, the member is deactivated in Pike from that date. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from the end date.Log time once
With Send time to Timmi Timesheet on, your team logs time against projects in Pike. Closing the pay period sends the approved hours to Timmi Timesheet, so nobody types the same week into Lucca.Deletes and removed records
An integration never deletes Pike data. A user deleted in Lucca is marked Removed in Lucca on the member, stays in Pike with their history, and stops syncing. A leave canceled in Lucca 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 writes to Lucca only to send approved time to Timmi Timesheet, and only when Send time to Timmi Timesheet is on.
- Timmi Timesheet entries do not import into Pike. Members log their time in Pike.
- Pending, denied or canceled leave requests do not sync.
- Compensation does not sync. Set cost profiles in Pike.
- The API key syncs only the users and data its rights allow.
Disconnect
Go to Workspace settings → Integrations → Lucca and click Disconnect. Syncing stops and every member, team, position, work schedule and time off entry stays in Pike with its history. Time already sent to Timmi Timesheet stays in Lucca. Reconnecting the same Lucca account 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.
- Pay periods and payroll: Period close and approved time.
- PayFit: Collaborators, contracts and absences.
- Factorial: Employees, contracts, leaves and compensation.