What syncs
Every approved timesheet is split into pay types first (regular, overtime, double time, holidays, break premiums, time off), using each site’s rules. Here’s where each lands in Humi.
| ClockLap | Sent as | Notes |
|---|---|---|
| Each finished shift | A time worked entry | Start and end time, on the primary hourly rate |
| Regular hours and holiday hours worked | hours | – |
| Overtime | overtime_hours | – |
Humi’s Partners API is in closed beta. Double time and time off aren’t sent through it; salaried people (no hourly rate in Humi) are listed as not sent.
How it works
- Request a Partners API tokenEmail [email protected] with the subject “Requesting Humi Partners API Token”. One token covers one company.
- Match peopleBy email; saved as each person’s Humi employee ID.
- Choose when to send, and reviewEach period yourself, on lock, when everything is approved, or on a schedule.
Schedules and review
Choose when hours go to Humi. Whatever you pick, nothing is sent twice: each period has one send, and anything after it is a correction.
I’ll send each period myself
Nothing goes until an admin presses Send. The default.
When the pay period is locked
Locking the period in Timesheets starts the send.
When every timesheet is approved
The last approval in the period starts the send.
On a schedule
A set number of days after the period ends (0 to 14), at a local time you pick.
- Which timesheets. Approved only (default), or approved and submitted.
- Rounding. Hundredths of an hour (default) or quarter hours.
- Split by. None, location, project or department, each mapped to the payroll system’s department or cost centre code.
- Holiday hours worked. As their own pay type (default) or folded into regular hours.
- Empty lines. People with no hours in the period are skipped.
- Unmatched people. Skip them and warn (default), or block the whole send until they’re matched.
Corrections, as changes
Fixed a missed clock-out after payroll went? Send the period again and ClockLap works out what changed since the last send.
A changed shift is updated in place by its Humi time worked ID, so nothing is added twice.
People
Matched by email.
Connect Humi a second time for people sync.
- Employees: name, email, department, position, office, hourly pay rate, start and end dates
Time off isn’t synced with Humi yet.
- Who wins, per field. The HR system by default: ClockLap is updated to match. Set any field to “ClockLap” and it’s only filled in when the person is added.
- New people. Added automatically, without an invite unless you turn invites on. You choose the role they get.
- People who leave. Suggested for turning off (default), or turned off automatically. Their history stays.
- Sites and teams. Map the HR system’s locations or departments to ClockLap sites once; moves follow on every sync.
- Single sign-on users. People your identity provider manages through SCIM keep what SCIM writes; the sync skips those fields and says so.
- Schedule. Hourly, daily (default) or manual. A scheduled sync can apply itself or only prepare a preview for an admin.
What you need
- Humi payroll (Canada) with hourly employees
- A Humi Partners API token for your company
Every run keeps a history: who and what was sent, per-line results, plain-language errors with a fix, and a redacted request log for admins. Webhooks fire on payroll.run_ready, payroll.run_sent, payroll.run_failed, people_sync.completed.
Questions
Is Humi’s API stable?
Humi describes its Partners API as a closed beta that can change, which is why this connection is marked beta.
Is the Humi connection included in the price?
Yes. Payroll and HR connections are part of every ClockLap plan: $1 per staff member and $2 per manager or admin a month, with no add-ons.
Is ClockLap affiliated with Humi?
No. ClockLap connects to Humi using its published API; it isn’t affiliated with or endorsed by Humi. The connection is in beta while we verify it with live accounts.