Clockify
Sync the workspace's entries into Clockify — connect several accounts, route projects, and map each teammate to their Clockify user.
If your work also lives in Clockify, connect it so tracked entries flow there automatically — useful when a tool or a client expects the data in their own Clockify. Clockify is a workspace integration: an admin connects the company's Clockify once, and everyone's routed time syncs to it. You can connect more than one Clockify account and send each project to whichever one it belongs to.
Clockify is connected once for the whole workspace, not per person. Connecting, routing projects, and mapping members needs the Manage workspace integrations permission (Owners and Admins have it by default; grant it to other roles under Settings → Roles & permissions). Everyone else sees it as connected but read-only.
Connect an account
In Clockify, open Profile Settings → API and generate/copy the API key. To sync a whole team, use a key from a Clockify workspace admin (see the callout under Sync your team's time).
Go to Settings → Apps & integrations → Clockify, click Connect, give it a label (e.g. Acme's Clockify) so you can tell accounts apart, and paste the key.
Use + Add account to connect another Clockify — for a second client, or a personal one alongside a client's. Each account keeps its own set of Clockify projects and its own team.
Sync your team's time
Each person's time syncs on behalf of their own Clockify user, so it lands under the right name in Clockify — not under whoever connected the account. Whoever connected it syncs as themselves automatically; map everyone else in Team member sync.
In the Clockify panel, find Team member sync. It lists your workspace's people.
For each person, pick their Clockify user. Leave someone unmapped and their time simply won't sync yet — you'll see a count of who still needs mapping.
Syncing on behalf of teammates uses Clockify's admin API, so the connected key must belong to a Clockify workspace admin. With a limited key, ProjectPacer can't list the workspace's members — you'll see a note to reconnect with an admin key. (Your own time still syncs regardless.)
An unmapped person's entries stay in ProjectPacer, waiting. Map them and run Sync now, and their past time flows across — nothing is dropped or mis-attributed in the meantime.
Route each project
A tracked entry follows its project's routing: which Clockify account, and which project inside that account.
In the Project routing table, choose the Clockify account a project should sync to. (With a single account connected, this step is automatic — you just pick the project.)
Choose the project inside that account. From then on, entries on that project sync there.
This is the point of multiple accounts: Acme projects can sync to Acme's Clockify while Globex projects sync to Globex's — all from one place, at the same time.
What syncs
- A completed entry on a routed project is created in its account's Clockify (and kept in step if you edit it afterward).
- A running entry isn't sent until you stop it.
- Entries on projects that aren't routed stay in ProjectPacer only.
- An entry whose owner isn't mapped to a Clockify user waits until you map them.
- Sync now back-fills past entries that haven't been pushed yet.
An entry only syncs once its project has an account and a Clockify project chosen. If entries aren't showing up in Clockify, an unfinished routing is usually why.
Disconnecting
Disconnect any account from the same screen. Entries already synced stay in Clockify — disconnecting just stops new ones from going to that account, and any projects routed to it become unrouted until you point them somewhere else.
Keys are encrypted at rest and used only to talk to Clockify on the workspace's behalf. Removing a connection deletes its key and its member mappings.