Overview
This article catalogs the error messages the Clockify integration can record in the iPaaS.com error logs (Dashboard / Integration Monitoring / Error Logs), grouped by flow. Each error carries a stable error code so you can find it here quickly: search this page for the code. Every entry lists the code, the message you see, what causes it, and how to resolve it. Parts of a message in braces, such as {action} or {id}, are filled in with the details of the transfer. When Clockify itself refused a request, the message ends with Clockify's own explanation after "Clockify said:". Where a resolution needs a change to mappings, filters or subscription settings, your Managed Integration Service Provider (MiSP), the partner who configures and supports your integration, can make it for you.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Settings
All Clockify Transfers
Customer Company FROM iPaaS.com
Customer Company TO iPaaS.com
Employee TO iPaaS.com
Timesheet TO iPaaS.com
Webhook Triggers
Error Collection
Connection and Settings
API Key setting empty
CLKF-AUTH-1001 - The API Key setting is empty. In Clockify open profile picture > Preferences > Advanced > Manage API keys, generate a key as a workspace owner or admin, and paste it into the subscription's API Key setting.
Description: The subscription's API Key setting is blank. The integration stops before calling Clockify.
Resolution: In Clockify, generate an API key as a workspace owner or admin (Profile settings > Preferences > Advanced > Manage API keys > Generate new), save it in the subscription's API Key setting, and retry the transfer.
Workspace Id setting empty or invalid
CLKF-AUTH-1003 - The Workspace Id setting is empty or isn't a Clockify workspace id. In Clockify open the workspace's Settings page and copy the address (or the 24-character id after /workspaces/) into the subscription's Workspace Id setting.
Description: Workspace Id is blank, or no 24-character Clockify workspace id can be read from it (for example, an API key was pasted there).
Resolution: Open the workspace's Settings page in Clockify, copy the address from the browser's address bar (or the 24-character id after /workspaces/), paste it into Workspace Id, and retry the transfer.
API key's user not in the workspace
CLKF-AUTH-1004 - The API key's Clockify user isn't a member of workspace {id}. Check the Workspace Id setting, or use the API key of a member of that workspace.
Description: Clockify accepts the API key, but its user does not belong to the workspace named in Workspace Id. A common cause is the workspace id shown in the CAKE.com account console, which is a different id from Clockify's.
Resolution: Copy the workspace id from the address bar of the workspace's Settings page in Clockify into Workspace Id, or use the API key of an owner or admin of that workspace. Then retry the transfer.
API Url isn't a Clockify address
CLKF-AUTH-1005 - The API Url setting isn't a Clockify address. Leave it blank for the global server, or enter your region's address such as https://euc1.clockify.me/api.
Description: API Url is not an https address on clockify.me. The integration refuses it before the API key is sent anywhere.
Resolution: Leave API Url blank for Clockify's global server, or enter the https address of your workspace's Clockify region (for example https://euc1.clockify.me/api), then retry the transfer.
Connection check failed
CLKF-EXTN-1003 - Clockify didn't answer the connection check (HTTP {status}). Check the API Url setting (blank for the global server, or the regional address such as https://euc1.clockify.me/api).
An optional setting has a value that isn't valid
CLKF-VALD-1001 - The Timesheet Mode setting isn't one of its values. Choose "Time entries" or "Approved weeks", or leave it blank for "Time entries".
CLKF-VALD-1001 - The Timesheet Poll Days setting isn't a whole number of days. Enter a number from 1 to 366, or leave it blank for 7.
CLKF-VALD-1001 - The Page Size setting isn't a whole number. Enter a number from 1 to 1000, or leave it blank for 50.
Description: Timesheet Mode, Timesheet Poll Days or Page Size holds a value the integration can't use. The value itself is never shown, in case it is a pasted API key.
Resolution: Correct the setting the message names, or clear it to use its default, then retry the transfer.
Workspace Id changed on a subscription that was used before
CLKF-BIZL-1001 - The Workspace Id setting now names a different Clockify workspace than this subscription used before. Its poll positions were reset, so the next polls start from the poll window in the new workspace; records linked in the old workspace aren't updated through this subscription. To connect another workspace, create a new subscription instead, and turn this one's Clockify triggers off first.
Description: A warning in the transfer's activity log, not a failed transfer: Workspace Id was changed after the subscription had run against another workspace. Records linked in the old workspace are not updated through this subscription. At the time this documentation was written, the subscription's poll positions keep their old values, despite what the message says.
Resolution: To connect another workspace, change Workspace Id back and create a new subscription for the other workspace, turning the old subscription's Clockify triggers off first so its webhooks are removed.
All Clockify Transfers
API key rejected by Clockify
CLKF-AUTH-1002 - Clockify rejected the API key while trying to {action}. Generate a new key in Clockify (profile picture > Preferences > Advanced > Manage API keys) as a workspace owner or admin and save it in the subscription's API Key setting.
CLKF-AUTH-1002 - Clockify rejected the API key. Generate a new key in Clockify (profile picture > Preferences > Advanced > Manage API keys) as a workspace owner or admin and save it in the subscription's API Key setting.
Description: Clockify does not accept the API key: it was deleted, mistyped, or belongs to another Clockify account. The second form comes from the connection check before a transfer.
Resolution: Generate a new API key in Clockify as a workspace owner or admin, save it in the subscription's API Key setting, and retry the transfer.
Clockify user lacks permission
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.
Description: Clockify refused the request as forbidden. Usually the API key's user is not a workspace owner or admin, or lost that role; creating webhooks and reading other members' time need it. At the time this documentation was written, the same message also appears when Timesheet Mode is Approved weeks on a Clockify plan without timesheet approval (approval is part of the Standard plan and higher, per Clockify pricing, read 2026-11-04); in that case the key is not the cause.
Resolution: Use the API key of a workspace owner or admin. If the key already belongs to an owner or admin and Timesheet Mode is Approved weeks, change Timesheet Mode to Time entries, or move the workspace to a Clockify plan with timesheet approval.
Clockify record not found
CLKF-NFND-1001 - Clockify couldn't find the record while trying to {action}. It may have been deleted, or the Workspace Id setting names another workspace.
Description: Clockify answered that the record does not exist, or that it does not belong to the workspace named in Workspace Id.
Resolution: Check that the record still exists in Clockify, in the workspace named by Workspace Id. A record deleted in Clockify can't be transferred; dismiss the error.
Clockify error or no answer
CLKF-EXTN-1001 - Clockify didn't answer normally while trying to {action} (HTTP {status}). Try again later; if it repeats, check status.clockify.me.
Description: Clockify had a server error or did not answer.
Resolution: Retry the transfer later. If it keeps failing, check Clockify's service status at status.clockify.me.
Clockify request limit reached
CLKF-EXTN-1002 - Clockify's request limit was reached while trying to {action}; iPaaS.com retries automatically.
Description: The workspace used up Clockify's request allowance, which Clockify counts per workspace across every API key using it: 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 this happens, 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.
Resolution: If the record hasn't arrived an hour or so after the limit frees up, resend it with Manual Sync. Frequent limits on the Free plan mean more polling or records than 30 requests an hour allows: schedule polls less often, or move the workspace to a paid Clockify plan.
Clockify refused the data
CLKF-EXTN-1008 - Clockify refused the data while trying to {action}. Clockify said: {message}
Description: Clockify rejected the request as invalid and gave a reason, which the message quotes (personal details are masked).
Resolution: Correct the value Clockify names, in the mapping or in the source record, then retry the transfer.
Unsupported data type or direction
CLKF-BIZL-1004 - Clockify doesn't support {data type}; remove or turn off that mapping collection.
CLKF-BIZL-1004 - Clockify members aren't created, changed or removed FROM iPaaS.com by this integration: Employee goes TO iPaaS.com only. Remove or turn off the Employee FROM iPaaS.com mapping collection.
CLKF-BIZL-1004 - Clockify time isn't created, changed or removed FROM iPaaS.com by this integration: Timesheet goes TO iPaaS.com only. Remove or turn off the Timesheet FROM iPaaS.com mapping collection.
CLKF-BIZL-1004 - Timesheet entries move only inside their timesheet, TO iPaaS.com. Remove or turn off any other Timesheet Entry mapping collection.
Description: The subscription has a mapping collection for a data type or direction the integration does not support. The integration supports Customer Company TO and FROM iPaaS.com, Employee TO iPaaS.com, and Timesheet (with its entries) TO iPaaS.com.
Resolution: Remove or turn off the mapping collection the message names.
Internal error
CLKF-INTL-1001 - The Clockify integration couldn't {step} a {data type} record: it received a record it doesn't handle. Retry the transfer; if it fails again, send this message to iPaaS.com Support.
Description: The integration received a record of a type it does not handle in that step.
Resolution: Retry the transfer. If it fails again, send the message, the subscription and the record's id to your MiSP, who can raise it with iPaaS.com Support.
iPaaS.com API call failed
CLKF-INTL-1002 - iPaaS.com could not complete {action} (HTTP {status}). Try again; if it repeats, contact iPaaS.com support.
Description: A lookup the integration makes in iPaaS.com, such as finding a matching company or employee, failed.
Resolution: Retry the transfer. If it repeats, send the message to your MiSP, who can raise it with iPaaS.com Support.
Customer Company FROM iPaaS.com
Several Clockify clients with the same name
CLKF-BIZL-1002 - Clockify has {n} clients with this company's name ({ids}), so the integration can't tell which one it is. Rename or archive the duplicates in Clockify, then retry.
Description: When a company was sent to Clockify, the name search found more than one Clockify client with the company's name, ignoring case.
Resolution: Rename the extra clients in Clockify so that only one has the company's name, then retry the transfer.
Client edited in Clockify since the integration's last write
CLKF-BIZL-1003 - Clockify client {id} was edited in Clockify ({fields}) since the integration last wrote it, so this update would overwrite that edit. To keep Clockify's version, dismiss this error and let the Clockify change reach iPaaS.com. To overwrite it, delete the [iPaaS.com sync …] line at the end of the client's note in Clockify and resend.
Description: The fields the message names were changed in Clockify after the integration last wrote the client, and that change has not reached iPaaS.com yet. The integration protects the Clockify edit.
Resolution: To keep Clockify's version, dismiss the error and let the Clockify change reach iPaaS.com (a client webhook trigger or client/poll). To overwrite it, delete the [iPaaS.com sync …] line at the end of the client's note in Clockify, then resend the company.
Client delete not supported
CLKF-BIZL-1005 - Clockify clients aren't deleted by this integration; archive the client instead (map Archived).
Description: A delete was sent FROM iPaaS.com. The integration never deletes Clockify clients.
Resolution: To retire a client, map Archived to true in the Customer Company FROM iPaaS.com collection, or archive the client in Clockify.
Clockify returned no client id
CLKF-EXTN-1004 - Clockify accepted the new client but returned no id. Retry; the integration then finds and links the client it made.
Description: Clockify accepted a new client but its answer carried no id.
Resolution: Retry the transfer. The integration finds the client it made by name and links it.
Client created but archived flag or currency refused
CLKF-EXTN-1010 - Clockify created client {id} but refused its archived flag or currency: {reason} The client is linked; correct the value and resend.
Description: The archived flag and currency are set with a second request after the client is created, and Clockify refused that request. The client exists in Clockify and is linked to the company.
Resolution: Correct the Archived or CurrencyId mapping (or the company's value), then resend the company.
Linked client deleted in Clockify
CLKF-NFND-1002 - Clockify client {id} no longer exists (deleted in Clockify). Remove the company's Clockify link in iPaaS.com to create it again.
Description: An update FROM iPaaS.com reached a client that was deleted in Clockify.
Resolution: To create the client again, the company's link to the deleted Clockify client must be removed in iPaaS.com first; ask your MiSP to remove it (or iPaaS.com Support if your MiSP can't), then resend the company.
Update without a linked client
CLKF-VALD-1002 - The company has no linked Clockify client, so it can't be updated. Use an Add/Update collection (it creates or links the client), or send the company once with it by Manual Sync.
Description: An update-only collection reached a company that was never linked to a Clockify client.
Resolution: Use an Add/Update collection, which creates or links the client, or send the company once with it by Manual Sync.
Company has no name
CLKF-VALD-1003 - The company has no name; Clockify requires a client name. Map Name in the Customer Company FROM iPaaS.com collection.
Description: The mapped company name is empty. Clockify requires a name on every client.
Resolution: Map Name in the Customer Company FROM iPaaS.com collection, or give the company a name, then retry.
Company name too long
CLKF-VALD-1004 - The company name is {n} characters; Clockify allows 100. Shorten the name in iPaaS.com, or map a shorter value to Name, then resend.
Description: The mapped name is longer than Clockify's 100-character limit for client names.
Resolution: Shorten the company's name in iPaaS.com, or map a shorter value to Name, then resend.
Address or note too long
CLKF-VALD-1005 - The address is longer than Clockify's 3000 characters, or the note longer than 2936 (the integration keeps a short sync mark at its end). Shorten the value in iPaaS.com, or map a shorter one, then resend.
Description: The mapped address is longer than 3,000 characters, or the note longer than 2,936. The integration keeps a short sync line at the end of the client's note.
Resolution: Shorten the value in iPaaS.com, or map a shorter one, then resend.
Currency not in the workspace
CLKF-VALD-1006 - The mapped currency isn't one of the Clockify workspace's currencies. Add it in Clockify's workspace settings, or map a code the workspace has.
Description: The mapped currency code or id is not set up in the Clockify workspace. It is checked before anything is written. A currency other than the workspace's own needs a Clockify plan with multiple currencies, Pro and higher (Clockify pricing, read 2026-11-04).
Resolution: Add the currency to the Clockify workspace, or map a currency code the workspace already has, then resend.
Customer Company TO iPaaS.com
Client's name matches several companies, or a company already linked to another client
CLKF-BIZL-1008 - iPaaS.com has {n} companies named "{name}" ({ids}), so the integration can't tell which one Clockify client {id} is. Rename or merge the duplicates in iPaaS.com, then retry.
CLKF-BIZL-1008 - iPaaS.com company {id} named "{name}" is already linked to Clockify client {other}, so Clockify client {id} can't be linked to it too. Give the two clients different names in Clockify, then retry.
Description: A new Clockify client is matched to the iPaaS.com company with the same name. The first form appears when the match finds more than one company; the second when the one company with that name is already linked to another Clockify client of this subscription (for example, a client renamed in Clockify to another client's earlier name).
Resolution: For the first form, rename the duplicate companies in iPaaS.com so that only one has the client's name, then retry. For the second, give the two clients different names in Clockify, then retry.
Employee TO iPaaS.com
Member's email matches several employees, or an employee already linked to another member
CLKF-BIZL-1006 - iPaaS.com has {n} employees with Clockify member {id}'s email ({ids}), so the integration can't tell which one this member is. Merge or change the duplicates in iPaaS.com, then retry.
CLKF-BIZL-1006 - iPaaS.com employee {id} with Clockify member {member}'s email is already linked to Clockify member {other}, so it can't be linked twice. Check the two members' emails in Clockify, then retry.
Description: A new Clockify member is matched to the iPaaS.com employee with the same email. The first form appears when more than one employee has that email; the second when the one employee with that email is already linked to another Clockify member of this subscription.
Resolution: For the first form, change the email on the duplicate employees in iPaaS.com so that only one has the member's email, then retry. For the second, check the two members' emails in Clockify (each person needs their own), then retry.
Timesheet TO iPaaS.com
Employee couldn't be sent first
CLKF-EXTN-1006 - Couldn't send Clockify {type} {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.
Description: A timesheet's member was not yet linked to an iPaaS.com employee, and sending the member as an employee first failed for the reason given.
Resolution: Turn on the Employee TO iPaaS.com collection and make sure its filter includes this member, fix the reason the message gives, then retry the timesheet.
Clockify user not linked to an iPaaS.com employee
CLKF-NFND-1003 - Clockify 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.
CLKF-NFND-1003 - The Clockify timesheet names no user, so it has no employee. Check the time entry or approval in Clockify, then retry the timesheet.
Description: The timesheet's employee can't be found in iPaaS.com, for one of the reasons the first message names, or the Clockify time entry or approval names no user.
Resolution: Turn on the Employee TO iPaaS.com collection, widen its filter or restore the employee, send the member TO iPaaS.com (for example with member/poll), then retry the timesheet from the error log.
Webhook Triggers
Webhook trigger doesn't fit the Timesheet Mode
CLKF-BIZL-1007 - The {scope} trigger doesn't apply in Timesheet Mode "{mode}". Use {scopes} instead, or change Timesheet Mode.
Description: A timesheet webhook trigger of the other Timesheet Mode was turned on. It is refused before Clockify is asked.
Resolution: Turn on the triggers the message names for the current Timesheet Mode.
Webhook address or key missing
CLKF-EXTN-1005 - iPaaS.com didn't supply this subscription's webhook address; save the subscription, then turn the webhook off and on again.
CLKF-EXTN-1005 - iPaaS.com didn't supply this subscription's webhook key; save the subscription, then turn the webhook off and on again.
Description: When a webhook trigger was turned on, iPaaS.com gave no webhook address or key to register with Clockify.
Resolution: Save the subscription, then turn the webhook trigger off and on again.
Clockify returned no webhook id
CLKF-EXTN-1007 - Clockify created the {scope} webhook but returned no id, so this subscription can't own it. Turn the scope off and on again.
Description: Clockify's answer to creating the webhook carried no id, so the subscription can't recognize the webhook as its own.
Resolution: Turn the trigger off and on again.
Clockify webhook limit reached
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.
Description: Turning on the trigger would pass Clockify's webhook limit, which also counts webhooks other tools made in the workspace (or, on paid plans, for the API key's user). Clockify allows 3 webhooks per workspace on the Free plan; 10 per user, up to 100 per workspace, on the Basic, Standard and Pro plans; and 100 per user, up to 300 per workspace, on Enterprise (Clockify API documentation, read 2026-11-06).
Resolution: Turn off a webhook trigger you need less, or schedule the data type's poll scope (client/poll, member/poll or timesheet/poll) instead. A workspace owner or admin can review the workspace's webhooks in Clockify under Preferences > Advanced > Manage webhooks.