Time entries (the default, on every Clockify plan): each completed Clockify time entry becomes one timesheet with one entry.

Approved weeks (Clockify plans with timesheet approval): each approved Clockify week becomes one timesheet with all the week's entries, and a withdrawn approval of a week already sent updates the same timesheet.

Time entries mode: the Clockify time entry id (example: 6aeca2c50afeb40f8398adb9).

Approved weeks mode: the id of the week's Clockify approval request (example: 6aeca37c9e3fb42e84c7a145).

Timesheet: iPaaS.com saves the same Clockify id (the time entry id, or the approval request id) on a dedicated external-ID record for the timesheet. That link is the match for later transfers, so an edited or restored entry, or a withdrawn approval, updates the same timesheet instead of adding another one.

Timesheet Entry: each entry is linked by the timesheet's Clockify id and the time entry id, joined by a vertical bar: {timesheet id}|{time entry id}. In Time entries mode both parts are the same time entry id (example: 6aeca2c50afeb40f8398adb9|6aeca2c50afeb40f8398adb9). In Approved weeks mode the first part is the approval request id (example: 6aeca37c9e3fb42e84c7a145|{time entry id}).

Status: Enabled (both collections). The default filter sends every timesheet.

Trigger Events: the Clockify webhook scopes of the chosen Timesheet Mode, enabled in the subscription's Inbound Data Flows section, and the timesheet/poll scope run by a scheduled poll event for the scope. No automatic transfers occur until a scope is enabled or the poll event is scheduled. Manual Sync is always available.

Parent Collection: Add/Update Clockify Timesheet TO iPaaS.com

Child Collection: Add/Update Clockify Timesheet Entry TO iPaaS.com: the timesheet's time entries, one in Time entries mode and every entry of the week in Approved weeks mode. It is a child of the Timesheet collection and runs only as part of its transfer; entries are never sent on their own.

Approved weeks needs timesheet approval in Clockify: timesheet approval is part of the Clockify Standard plan and higher (Clockify pricing, read 2026-11-04). At the time this documentation was written, on a plan without approval subscribers see CLKF-AUTZ-1001 - The Clockify user who owns the API key isn't allowed to {action}. Use the API key of a workspace owner or admin. The action names the approval read (for example reading the week's approval request, or listing approved Clockify timesheets). The cause is the plan, not the API key: changing the key does not help. Use Time entries mode, or move the workspace to a plan with timesheet approval.

Billable data needs a plan with billable time: billable status and billable hours need Clockify Basic or higher (Clockify pricing, read 2026-11-04). On a plan without it, validate what Clockify Billable and Clockify Billable Hours hold in a staging environment before relying on them in production.

Running timers wait: a time entry without an end is not sent; it is sent when the timer stops (the TIMER_STOPPED scope or the next poll).

Rejected and unapproved weeks: the integration does not send a rejected week or a week that was submitted but never approved. A withdrawn or pending week is sent only when its timesheet is already in iPaaS.com, so unapproved time is never added. A rejected week logs no error, and a withdrawn approval updates the timesheet already sent, and its entries, to WITHDRAWN_APPROVAL.

The poll reads a window: in Time entries mode the poll reads entries by their start date, within Timesheet Poll Days (1 to 366, default 7); an edit to an older entry arrives only by webhook or Manual Sync. In Approved weeks mode the poll sends approved weeks only, within that window; a withdrawn approval arrives only by webhook or Manual Sync, whatever its age.

Rate limits: Clockify allows 30 requests per hour on the Free plan, 20 per second on the Basic, Standard and Pro plans, and 50 per second on Enterprise (Clockify API documentation, read 2026-11-06). When the limit is reached, the transfer stops with CLKF-EXTN-1002. The code and iPaaS.com's message that the transfer will be retried later appear in the transfer's activity log; no error is added to the Error Logs. While the limit lasts, iPaaS.com also holds this subscription's other transfers in the same direction. If the record hasn't arrived an hour or so after the limit frees up, resend it with Manual Sync. In Time entries mode, a poll that reaches the limit keeps its place and continues from there at the next run.

Webhook limits: Clockify allows 3 webhooks per workspace on the Free plan; 10 per user (the owner of the API key) and 100 per workspace on the Basic, Standard and Pro plans; and 100 per user and 300 per workspace on Enterprise (Clockify API documentation, read 2026-11-04). A scope that would pass the limit is refused with CLKF-EXTN-1009; use timesheet/poll instead.

Local work date: an entry's Date is the day the person worked in a local time zone: the time zone Clockify records for the entry; in Approved weeks mode, when the entry has none, the time zone of the person whose week it is; and when neither is available, the UTC day of the entry's start. An evening entry west of UTC therefore keeps its local day. All start and end times are in UTC. Subscribers whose people work far from UTC should validate the dates of a few late-evening entries in a staging environment before relying on them in production.

A timesheet needs its employee: the EmployeeId mapping finds the iPaaS.com employee linked to the Clockify member. Keep Add/Update Clockify Employee TO iPaaS.com enabled, with a filter that includes everyone whose time you send.

Custom fields: the default mappings write six iPaaS.com custom fields: Clockify Approval State and Clockify Billable Hours on the timesheet, and Clockify Project, Clockify Client, Clockify Task and Clockify Billable on each entry. If a custom field doesn't exist in your iPaaS.com company, create it with exactly this name before the first transfer; the Clockify Installation Instructions list them.

CLKF-NFND-1003 - Clockify user {user id} isn't linked to an iPaaS.com employee, so the timesheet has no employee: the Employee TO iPaaS.com mapping collection is off, its filter leaves this member out, or the employee was deleted in iPaaS.com. Fix that, send the member, then retry the timesheet. Turn on the Employee TO iPaaS.com collection, widen its filter or restore the employee, send the member, then retry the timesheet from the error list. When the Clockify record names no user at all, the same code reads The Clockify timesheet names no user, so it has no employee. Check the time entry or approval in Clockify, then retry the timesheet.

CLKF-EXTN-1006 - Couldn't send Clockify employee {user id} to iPaaS.com first: {reason} Check that the Employee TO iPaaS.com collection is on and its filter includes this member, then retry the timesheet. The member could not be sent first; fix the reason given in the Employee TO iPaaS.com collection, then retry the timesheet.

CLKF-BIZL-1007 - The {scope} trigger doesn't apply in Timesheet Mode "{mode}". Use {scopes} instead, or change Timesheet Mode. A webhook scope of the other mode was turned on. Turn on the scopes that match the Timesheet Mode setting.

CLKF-AUTZ-1001 - The Clockify user who owns the API key isn't allowed to {action}. Use the API key of a workspace owner or admin. At the time this documentation was written, this is what subscribers see in Approved weeks mode on a Clockify plan without timesheet approval; there the plan is the cause (see Clockify Caveats). Otherwise, use the API key of a workspace owner or admin.

CLKF-EXTN-1002 - Clockify's request limit was reached while trying to {action}; iPaaS.com retries automatically. The code and iPaaS.com's message that the transfer will be retried later appear in the transfer's activity log; no error is added to the Error Logs. While the limit lasts, iPaaS.com also holds this subscription's other transfers in the same direction. If the record hasn't arrived an hour or so after the limit frees up, resend it with Manual Sync. Frequent occurrences on the Free plan mean too much polling for 30 requests per hour.

CLKF-EXTN-1009 - Clockify refused the {scope} webhook: Clockify's webhook limit is reached (3 per workspace on the free plan; 10 per user, the owner of the API key, on paid plans). Turn off another Clockify webhook scope, or use this data type's poll scope instead. Turn off a webhook scope you need less, or schedule timesheet/poll. The plan limits are listed under Clockify Caveats.

Timesheet Mode is the one you want, chosen before the first transfer, and only that mode's webhook scopes are on.

In Approved weeks mode, the Clockify workspace is on a plan with timesheet approval; for billable data, on Basic or higher.

The six timesheet and entry custom fields exist in your iPaaS.com company.

Add/Update Clockify Employee TO iPaaS.com is enabled and its filter includes everyone whose time you send.

A poll event for timesheet/poll is scheduled if you rely on polling.

First load: there is no separate initialization; the first timesheet poll goes back Timesheet Poll Days, up to 366 days.

Payroll and job costing: Approved weeks mode adds only approved time and shows withdrawn approvals, which suits payroll; Time entries mode sends every completed entry as it is tracked, which suits job costing.

iPaaS.com <> Clockify: Background

Clockify Installation Instructions

Clockify Connections and Settings

Clockify Mapping Functions

Clockify API Endpoints

Clockify Error Messages

Clockify Known Limitations

Clockify to iPaaS.com Employee Mapping Documentation

Clockify plans and pricing (timesheet approval Standard and higher, billable time Basic and higher, cost rates and multiple currencies Pro and higher)

Clockify API documentation (rate limiting, and webhooks per workspace and per user)