ClockLap + Namely: people in sync

What syncs

Namely is the source of truth for people. On each sync ClockLap reads:

• Profiles: name (preferred first), email, employee ID, job title, department and office (from Namely groups), manager, start and departure dates, status

How it works

1. Create a personal access tokenIn Namely: API → Personal Access Tokens, as an administrator (ideally an “Integrations” profile that won’t leave).
2. Paste it with your subdomainThe part before .namely.com.
3. Map departments and officesTo ClockLap teams and sites.
4. Review the dry runThen apply it and choose the schedule.

Matching people

Matched by earlier links, then email and employee ID; saved as each person’s Namely profile ID.

• 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

• Namely (US) with API access for an administrator

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 people_sync.completed.

Questions