- Home
- Resources
- Integrations
- Clockify
Clockify Zapier integrationAutomate Clockify with Zapier.
The Clockify Zapier integration gives you 7 triggers, 7 actions and 6 searches to move clients, projects, tasks and timers in and out of Clockify. Below: what each one does, what it costs you, and where it tends to get stuck.
Verified Trustpilot reviews · AI, automation & growth agency
What the Clockify Zapier integration actually does
Hooking Clockify up to Zapier means one thing in practice: something happens in your time tracker (a client, a project, a timer) and Zapier reacts by doing something for you, in Clockify or in another app. You set it up once. After that, nobody copies a client name by hand anymore.
Three results people usually build first. A tidy project list: New Client fires, Create Project opens a project under that client, and the team stops logging hours against “Misc”. A timer that starts on its own: another app hands over an event, Start Timer launches the clock, and Stop Timer ends it later. A clean tag catalog: Find Tag looks before Create Tag writes, so the same label never exists twice.
What Zapier does not do for Clockify matters just as much. All seven triggers are polling triggers, so nothing here reacts the second a timer starts: on the free plan, the check comes every 15 minutes. There is no action to edit or delete an existing time entry, client or project. And the catalog has no trigger for a timer that stops, only for a new entry and for a timer that starts.
If those limits bother you, the same app exists on other platforms. Compare with the Clockify n8n integration and the Clockify Make integration before you commit.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new client, project or timer.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a Clockify task.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself. Every Clockify trigger polls.
- Filter
- A step that lets the Zap continue only when the incoming data matches your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something that already exists, like a Clockify project, so the next steps can reuse what it found.
What a Clockify Zap really costs
Clockify is not a premium app, so it works from the free plan onward.
- Free plan100 tasks a month
- Zaps on freeTwo steps only
- Premium appNo
- Trigger cost0 tasks
The trigger never costs a task, however often Zapier checks Clockify. Each action that succeeds counts once, so a Zap with three actions eats three times more than a Zap with one. A failed action costs nothing. The free plan gives you 100 tasks a month, but only two-step Zaps: one trigger, one action. Add a filter or a search and the Zap becomes a multi-step Zap, which needs a paid plan, whatever app sits inside it.
Connect Clockify to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Clockify account linked to Zapier once, then reused by every step that touches Clockify.
- 02
Pick Clockify
Type Clockify in the search box of the dialog, select it, then click Add connection. Clockify then opens in a new browser tab, where the next step happens.
- 03
Sign in and grant access
Log in to Clockify in that tab and allow Zapier to reach the account. Use the account that actually belongs to the workspaces you want to automate: Zapier only sees what that login can see.
Your first Zap: a project for every new client
GoalEach time a client appears in Clockify, open a project for it and add a first task, so hours land in the right place from day one.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Clockify as the app and New Client as the event. Select your connection, then the Workspace the Zap should watch.
- 02
Test the trigger on real data
Run the test. Zapier brings back the three most recent clients of that workspace, so you map the next steps on a real one rather than on an empty shape.
- 03
Add Create Project
Add a Clockify action, pick Create Project, set the same Workspace and map the client name into the project name. Decide whether the project is public to the whole workspace.
- 04
Add Create Task
Add Create Task, choose the Workspace first, then the Project field fills up. Map the project created just before and type a task name such as Kickoff.
- 05
Test each step, then publish
Test every step and read what came back. This Zap has two actions, so it needs a paid plan. When it looks right, click Publish to switch it on.
Clockify triggers on Zapier
7 events start a Zap when something happens in Clockify. Zapier checks for them at the interval your plan allows.
New Client
Polling triggerIn Zapier“Triggers when a new client is added to a workspace.”
This one notices a client that someone added to a Clockify workspace and hands its name and details to the rest of your Zap. It is the natural starting point for anything that should exist once per customer, like a project or a folder.
New Project
Polling triggerIn Zapier“Triggers when a new project is added to a workspace.”
Fires on a project freshly added to a workspace. Your Zap gets the project and can react with tasks, tags, or a message elsewhere telling the team that a new job is open for tracking.
New Tag
Polling triggerIn Zapier“Triggers when a new tag is added to a workspace.”
Watches the tag list of a workspace and starts the Zap when a label appears. If your team sorts its hours with tags, a new one may deserve a reaction elsewhere.
New Task
Polling triggerIn Zapier“Triggers when a new task is added to a project on a specified workspace.”
Reacts to a task added under one specific project. It is the narrowest of the Clockify triggers: you aim it at a single project, and only tasks born there start the Zap.
New Time Entry
Polling triggerIn Zapier“Triggers when a new time entry is added.”
Picks up a time entry once it is added to the workspace. This is the trigger for anything built on hours that people already logged: reports, invoicing prep, or a weekly recap elsewhere.
New Timer Started
Polling triggerIn Zapier“Triggers when a new entry is started and running.”
Different from the previous one: it catches a timer the moment it is running, before anyone stops it. Your Zap knows that someone is on the clock now, and on which work.
New Workspace
Polling triggerIn Zapier“Triggers when a new workspace is created.”
The only Clockify trigger with no Workspace to pick, since its whole job is to spot a brand new one. It is the one to use if your organization opens new workspaces over time.
Clockify actions on Zapier
Clockify gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Task
ActionIn Zapier“Creates a task on a specified project.”
Adds a task under a project you point at, so the people tracking time can pick it instead of typing free text.
Create Client
ActionIn Zapier“Creates a client on a specified workspace.”
Writes a new client into a workspace from data that arrived in an earlier step, typically a signed deal or a form.
Create Project
ActionIn Zapier“Creates a project on a specified workspace.”
Opens a project in a workspace, with a name and two switches: public or not, billable or not.
Create Tag
ActionIn Zapier“Creates a tag on a specified workspace.”
Adds a label to the tag list of a workspace, ready to be put on time entries.
Create Time Entry
ActionIn Zapier“Creates a new time entry on a specified workspace.”
Logs a finished block of time, with a start and an end, on a workspace. You can also say whether it is billable.
Start Timer
ActionIn Zapier“Starts a new time entry.”
Starts a running timer on a workspace, the same as someone clicking start in Clockify, optionally flagged as billable.
Stop Timer
ActionIn Zapier“Stops currently running time entry on a specified workspace.”
Ends whatever timer is currently running on the workspace you pick. It needs no entry to point at, only the Workspace.
Clockify searches: find before you create
6 search steps look for data that already exists in Clockify, so a later step can use it.
A search step looks inside Clockify before the Zap writes anything. In the editor, searches sit at the bottom of the action list, under their own SEARCH heading. Each one below also has a find-or-create version: it is the same search with a box ticked, not an extra operation. Three settings decide what happens next.
Find Client
SearchFind or createIn Zapier“Finds a client by name on a specified workspace.”
Looks a client up by name in a workspace and hands its details to the next step, so you can attach a project to the right customer.
Find Project
SearchFind or createIn Zapier“Finds a project by name on a specified workspace.”
Finds a project by its name inside a workspace. The steps after it can then log time or add tasks to that exact project.
Find Running Timer
SearchFind or createIn Zapier“Finds a currently running time entry on a specified workspace.”
Checks whether a timer is currently ticking on the workspace and returns it if so. It only needs the Workspace.
Find Tag
SearchFind or createIn Zapier“Finds a tag on a specified workspace.”
Searches the tag list of a workspace for a given name, so a later step can apply an existing label.
Find Task
SearchFind or createIn Zapier“Finds a task by name on a specified project and workspace.”
Locates a task by name, but only inside one project of one workspace, so you must give both before the task name.
Find Time Entry
SearchFind or createIn Zapier“Finds a time entry by description, start datetime or end datetime.”
Looks for an existing entry by its description, its start or its end, within a workspace.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the later steps are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into find-or-create: the setting above disappears and the step asks for the fields it needs to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When a Clockify Zap breaks
Zapier attaches no help article to Clockify and no Clockify-specific limit is documented. What breaks is the general mechanics of Zapier, and four cases come back again and again.
Most problems show up in the Zap history as a step that did not run, or ran twice. Before you rebuild anything, read which case matches. The Zapier troubleshooting guide goes deeper when none of them fits.
Old entries are never picked up
A Zap only reacts to what happens after you switch it on. Clients, projects and hours that existed before stay out; moving that backlog is a separate job.The Zap keeps setting itself off
If a Zap creates tags in the workspace its New Tag trigger watches, each new tag starts it again and your task count drains fast.A bulk import gets held back
When a trigger suddenly returns a huge batch, say after importing a year of time entries, Zapier's flood protection can pause it before any action runs.No double runs on the same item
Zapier remembers what a polling trigger already saw, so the same client or entry does not start the Zap twice. Editing it later will not fire it again either.
Need help automating Clockify with Zapier?
A person reads every message.



