Integrate iPaaS.com with Clockify to enable seamless data synchronization for clients and companies (in both directions), and for members, timesheets and time entries (TO iPaaS.com).
How to Connect
Prerequisites
Before configuring the integration in iPaaS.com, set up API access in Clockify:
Choose the Clockify workspace to connect. One subscription connects one workspace.
Sign in to that workspace as a workspace owner or admin, and generate an API key under Profile settings > Preferences > Advanced > Manage API keys > Generate new. Clockify shows the key only once, so copy it right away (Clockify Help Center: profile settings, read 2026-11-06). Clockify's API follows the same permissions as the Clockify web app (Clockify API overview, read 2026-11-06), and only workspace owners and admins can create webhooks (Clockify Help Center: API and webhook settings, read 2026-11-06); the integration reads every member's time and creates webhooks, so the key must belong to an owner or admin.
If your workspace is on its own Clockify subdomain, generate the key while signed in to that subdomain: Clockify issues a separate key for it (Clockify API documentation, read 2026-11-06).
To send approved weeks (Timesheet Mode Approved weeks), the workspace needs timesheet approval, which is part of the Clockify Standard plan and higher (Clockify pricing, read 2026-11-04).
Configuration Details
You will need the following values to connect:
API Key: the Clockify API key generated above. Example: the key you copied from Manage API keys.
Workspace Id: the 24-character id of the workspace. In Clockify, open the menu (...) next to the workspace's name, choose Workspace settings, and copy the id from the browser's address bar (the part after
/workspaces/), or paste the whole address. Use the id from Clockify itself: the workspace id shown in the CAKE.com account console is a different id and is refused. Example:6aebacf06c1026f0c54d849e.API Url: leave it blank, or enter Clockify's global server,
https://api.clockify.me/api, unless your workspace is hosted in a Clockify region. For a regional workspace, enter that region's address:https://euc1.clockify.me/api(EU, Germany),https://use2.clockify.me/api(USA),https://euw2.clockify.me/api(UK) orhttps://apse2.clockify.me/api(Australia) (Clockify API documentation, read 2026-11-06).
Configure Subscription Settings
In your iPaaS.com subscription, open the Clockify subscription settings and complete the fields below.
Field | Description | Required | Example |
API Url | The Clockify server the integration calls. Blank means the global server. A regional address must be a Clockify https address; any other address is refused with CLKF-AUTH-1005. A trailing | No | |
API Key | The API key of a workspace owner or admin. Sent to Clockify with every request. | Yes | (your Clockify API key) |
Workspace Id | The workspace to connect: the 24-character id, or any Clockify address that contains | Yes | 6aebacf06c1026f0c54d849e |
Timesheet Mode | A text field: type Time entries or Approved weeks. Time entries sends every completed time entry as a timesheet (all plans). Approved weeks sends every approved week as one timesheet with its entries (plans with timesheet approval). Blank means Time entries. See the DESTRUCTIVE SETTING note below. | No | Time entries |
Timesheet Poll Days | How many days back the timesheet poll reads: time entries by their start date, or, in Approved weeks mode, weeks whose approval was last updated in that period. A whole number from 1 to 366; blank means 7, and a value above 366 is treated as 366. The first poll uses it to bring in past time, so set it before that poll runs. A larger value reads more time on every poll and uses more Clockify requests. | No | 7 |
Page Size | How many records the integration asks Clockify for in each page of a list (reading one approved week always uses pages of 50). A whole number from 1 to 1000; blank means 50, and a value above 1000 is treated as 1000. Keep the default unless iPaaS.com Support advises otherwise. | No | 50 |
API Throttle Limit / API Throttle Seconds | The most calls iPaaS.com makes to Clockify in each window of that many seconds. Pre-populated by the integration. | Yes | 500 / 60 |
API Throttle Limit (To iPaaS) / API Throttle Seconds (To iPaaS) | The same limit for transfers TO iPaaS.com. Pre-populated by the integration. | Yes | 500 / 60 |
Concurrent Connections | The number of simultaneous connections to the Clockify API. Pre-populated by the integration. | Yes | 2 |
Concurrent Batch Executions | A platform setting the Clockify integration does not use. Leave it at its pre-populated value. | No | 10 |
DESTRUCTIVE SETTING: Workspace Id. Do not change Workspace Id on a subscription that has already transferred records. Records stay linked to the old workspace's clients, members and time, are no longer updated, and the old workspace's webhooks stay in Clockify; at the time this documentation was written, the timesheet poll also keeps its saved place from the old workspace. To connect another workspace, create a new subscription. If you are unsure, consult your MiSP (Managed Integration Service Provider) or implementation partner before proceeding: the recovery cost if the change is wrong is significantly higher than the consultation cost.
DESTRUCTIVE SETTING: Timesheet Mode. Do not change Timesheet Mode on a subscription that has already sent timesheets. The earlier timesheets stay, and the same hours are sent again in the new form, so a receiving payroll or billing system can count them twice. Choose the mode before the first timesheet sync. If you are unsure, consult your MiSP or implementation partner before proceeding: the recovery cost if the change is wrong is significantly higher than the consultation cost.
Authentication Methods
The integration authenticates to Clockify with the workspace API key:
Generate the API key in Clockify as a workspace owner or admin (see Prerequisites).
Enter the API Key, the Workspace Id and, for a regional workspace, the API Url in the subscription settings, and save.
iPaaS.com sends the API key to Clockify in a request header on every call. There is no sign-in step and no token to renew.
Before each transfer, the integration checks the settings and the connection with one call that reads the workspace.
When a setting is refused, the transfer's error reads "Unable to connect to subscription", and the reason, with a code that names the setting, is in the subscription's iPaaS.com logs. The codes are:
CLKF-AUTH-1001 or CLKF-AUTH-1003: API Key or Workspace Id is empty, or Workspace Id holds no workspace id.
CLKF-AUTH-1002: Clockify does not accept the key. Generate a new key and save it.
CLKF-AUTH-1004: the key's user isn't a member of the workspace in Workspace Id, for example when the CAKE.com console id was entered. Check Workspace Id.
CLKF-AUTH-1005: API Url isn't a Clockify address.
CLKF-EXTN-1003: Clockify didn't answer the connection check as expected, usually because API Url names the wrong region.
CLKF-VALD-1001: Timesheet Mode, Timesheet Poll Days or Page Size holds a value that isn't valid; the message names the setting.
If the key is deleted in Clockify, it stops working at once. Generate a new key, enter it in API Key, and save; nothing else changes.
Initialization Support
Currently, initialization is not supported for Clockify in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. Existing clients and members arrive with the first scheduled client/poll and member/poll runs, and past time with the first timesheet/poll run, as far back as Timesheet Poll Days. To send many existing iPaaS.com companies to Clockify at once, use bulk sync using Postman.
Throttling
Clockify limits API requests per workspace: 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). Every API key used on the workspace counts against the same limit. When a transfer reaches the limit, 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.
The integration's throttle and concurrency fields are pre-populated (500 calls per 60 seconds in each direction and 2 concurrent connections) and can be adjusted for your volume. On the Free plan these values do not keep transfers under Clockify's hourly limit. A time-entry poll of a large workspace can use up the hour's requests; the poll keeps its place and continues at the next run, so bringing in past time can take several runs. For details on how these fields behave, see Subscription Configuration – Edit.