Resources · Make integration

Clockify Make integrationAutomate Clockify with Make.

What if your timesheets filled themselves in while your team kept working? The Clockify Make integration gives you 36 modules, including 6 instant triggers and 22 actions. This guide shows ops leads and agency owners how to connect the account and ship a first working scenario.

Try the Clockify integration on Make See the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clockify Make integration do for you?

The Clockify Make integration links your Clockify account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick that watches, searches or acts. Clockify can call Make the moment a timer starts, a client appears or an entry changes, and Make can write time, projects and tasks back.

A client file that builds itself. Your sales tool closes a deal, and Make runs Add a Client, then Add a Project, then Add a Task. The account manager opens Clockify and the structure is already there, ready for the first timer.

Hours that land where finance reads them. Get a Detailed Report or Get a Summary Report pulls the numbers out of Clockify once a project wraps up, and the next module sends them to the sheet, CRM or invoicing tool your team already uses.

A timer that follows the real work. Watch Timers reacts when someone starts or stops the clock. Pair it with a message to a team channel, or use Stop a Time Entry when a ticket is closed elsewhere so nobody logs a phantom evening.

What Make does not do: the listed modules cover entries, projects, tasks, clients, tags, workspaces, reports and groups. For anything else, the Make an API Call module reaches the rest of the Clockify API, and the Clockify API documentation lists which endpoints exist. Clockify also has an n8n node, covered on the Clockify n8n integration page, and the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Clockify to Make?

01
Generate your API key in Clockify
Log in to Clockify, click your Profile icon in the upper right corner, then Profile Settings. Scroll down to the API section, click Generate and copy the key. This key is what lets Make act on your account.
02
Add a Clockify module in Make
In your scenario, add any Clockify module and click Create a connection. A connection is your Clockify account linked to Make once, then reused by every Clockify module. With an instant module, click Create a webhook first, then Create a connection.
03
Paste the key and save
Give the connection a name in Connection name if you like (handy when you manage several workspaces). Paste the key into the API Key field and click Save. Make can now list your Clockify data in every field.

First scenario

Your first scenario: a starter task on every new project

GoalWhen a project is created in Clockify, Make adds a first task to it so the team can start tracking right away.

01
Create the scenario
Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the canvas. That circle becomes your first module.
02
Set up Watch Projects
Search for Clockify, pick Watch Projects, then click Create a webhook and attach your Clockify connection. Clockify will now tell Make about each project you create.
03
Add the task module
Click the + on the right of the trigger and choose Add a Task. Map the project coming from Watch Projects, then type the task name, for example Kickoff. Make lists the values it can read, no need to remember any ID.
04
Test with Run once
Click Run once, then create a test project in Clockify. Each module shows the bundles it received: a bundle is one item passing from module to module, here one project. Check that the task appeared in Clockify.
05
Switch it on
Turn the scenario on. Because Watch Projects is instant, the scenario starts whenever Clockify calls Make. Each module run on a bundle counts as one operation, the unit Make tracks on your plan.

Triggers

Which Clockify events can start a scenario?

6 modules start a scenario when something happens in Clockify. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Clockify as soon as it happens.

Clockify1Watch Time Entries

Watch Time Entries

Instant trigger

In Make“Triggers when a time entry is created, updated or deleted.”

This trigger catches every move on a time entry: one gets created, edited or deleted, and your scenario starts with that entry in hand. It is the broadest watcher of the set.

How it fires

instant. Clockify calls Make through a webhook as soon as the change happens, which is what the lightning badge on the module means.

When to use it

you want a copy of logged hours in a spreadsheet or billing tool that stays in step with Clockify, corrections and deletions included.

Watch out

an edit and a deletion both start the scenario and cost operations. Check with Run once what each case sends before you switch it on.

Clockify2Watch Projects

Watch Projects

Instant trigger

In Make“Triggers when a project is created.”

Watch Projects wakes your scenario each time someone creates a project in Clockify. You get the new project as a bundle, ready to feed a task, a folder or a message.

How it fires

instant. Clockify sends the new project to Make by webhook the moment it exists, no polling involved.

When to use it

every project should come with the same starter tasks or a matching record in your project tool, and you are tired of setting that up by hand.

Watch out

it reacts to creation only. Renaming or archiving a project later does not start the scenario.

Clockify3Watch Tasks

Watch Tasks

Instant trigger

In Make“Triggers when a task is created.”

Here the signal is a brand new task inside a project. The scenario receives that task and can pass it on to whoever needs to know it exists.

How it fires

instant. Clockify calls Make through a webhook once the task is created, and the run begins straight away.

When to use it

a lead adds tasks in Clockify and the team works from another board, so each new task should appear there too without copy and paste.

Watch out

changes to an existing task do not count. If your flow creates tasks with Add a Task, make sure it does not loop back into this trigger.

Clockify4Watch Clients

Watch Clients

Instant trigger

In Make“Triggers when a client is created.”

A new client record in Clockify is enough to start this one. The scenario gets the client and can build everything that usually follows a signature.

How it fires

instant. As soon as the client is created, Clockify notifies Make through a webhook.

When to use it

the client is created in Clockify first and your CRM, accounting tool or shared drive should get a matching entry without anyone retyping the name.

Watch out

only creation triggers it. A client renamed later keeps its old name in the other tools unless you handle that update yourself.

Clockify5Watch Tags

Watch Tags

Instant trigger

In Make“Triggers when a tag is created.”

Tags are how many teams sort billable work, overtime or campaigns in Clockify. This trigger starts a run whenever a new tag is added to the workspace.

How it fires

instant. Clockify pushes each new tag to Make by webhook right after it is created.

When to use it

your reporting sheet or dashboard keeps a list of allowed tags and must stay aligned with what people actually create in Clockify.

Watch out

a tag created by your own scenario with Add a Tag starts this trigger too, so think about that loop before switching on.

Clockify6Watch Timers

Watch Timers

Instant trigger

In Make“Triggers when a timer is started or stopped.”

Watch Timers follows the stopwatch itself: it starts a run when someone launches a timer and again when they stop it. Of the six triggers, this one sits closest to live work.

How it fires

instant. Clockify calls Make by webhook the moment a timer starts or stops.

When to use it

you want a status in your chat tool that says who is working on what, or you want to flag a timer started on the wrong project.

Watch out

one timer session gives two runs, start and stop, so each session costs operations twice. Count two runs per session when you estimate your monthly usage.

Modules

What can Make do in Clockify?

Clockify gives you 30 modules in 9 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Time Entry

6 modules

Clockify1

Find Time Entries

In Make“Finds time entries for a specified user in a workspace.”

Pulls the time entries of one user in a workspace, so the scenario can loop over them one bundle at a time.

When to use it

a manager asks for everything a freelancer logged before you pay their invoice, and you want the list in a sheet rather than on screen.

Watch out

a search can return zero, one or many entries. The next modules run once per entry, which adds operations fast.

Clockify2

Get a Time Entry

Action

In Make“Gets the details of a time entry in a workspace.”

Reads a single time entry in full when you already know which one you want. Think of it as opening the entry card rather than searching the whole list.

When to use it

a trigger or another tool hands you an entry ID and you need its details, such as the project or description, before deciding what to do next.

Watch out

it needs a precise entry. Without one, start with Find Time Entries instead.

Clockify3

Run/Add a Time Entry

Action

In Make“Runs or adds a new time entry to a workspace.”

Two jobs in one module: it can start a running timer or record a block of time that already happened. Either way, the hours end up in the workspace you pick.

When to use it

a meeting ends in your calendar, a support ticket closes, or a form is submitted, and that effort should appear in Clockify without anyone typing it.

Watch out

starting a timer leaves it running. Plan a Stop a Time Entry step somewhere, or it keeps counting.

Clockify4

Update a Time Entry

Action

In Make“Updates a time entry in a workspace.”

Changes an entry that already exists instead of creating a second one. Useful to fix what people logged, or to enrich it with data from another tool.

When to use it

hours were logged on the right day but the wrong project, and a rule in your scenario knows where they belong, for instance from the ticket they came from.

Watch out

it overwrites the entry. If Watch Time Entries also runs on the same workspace, it will fire again on your own update.

Clockify5

Stop a Time Entry

Action

In Make“Stops currently running time entry in a workspace.”

Stops the timer that is currently running in a workspace, exactly like pressing the stop button in Clockify, but triggered by an event elsewhere.

When to use it

someone closes a ticket, ends a call or sets their chat status to away, and the running timer should end at that point instead of ticking all evening.

Watch out

it acts on the running entry only. If no timer is running, there is nothing to stop, so test that case with Run once.

Clockify6

Delete a Time Entry

Action

In Make“Deletes a time entry from a workspace.”

Removes a time entry from the workspace. Use it with care and treat the deletion as final.

When to use it

a duplicate entry was created by an earlier automation, or a test run left fake hours in a real project, and you want the cleanup done by the same scenario.

Watch out

run it only after a Get a Time Entry check on one exact entry, never directly after a search that may return many entries.

Project

5 modules

Clockify7

Find Projects

In Make“Finds projects by name in a workspace.”

Looks up projects by name in a workspace and returns what matches. It turns a readable name, such as a client name, into the project Make can work with.

When to use it

a form or CRM gives you a project name and you need the real Clockify project before logging time or adding a task to it.

Watch out

similar names can return several projects. Check the bundles in Run once before you trust the first match.

Clockify8

List Project Custom Fields

In Make“Retrieves a list of a project's custom fields.”

Returns the custom fields attached to one project. If your team uses custom fields in Clockify to hold extra info, this is how Make reads them.

When to use it

you are building a report or a sync that should carry those extra project details along, and you first need to see which fields exist on that project.

Watch out

it lists fields for one project at a time. Run it on a real project in Run once to see what comes back.

Clockify9

Get a Project

Action

In Make“Retrieves an existing project.”

Fetches one existing project with its details, when the scenario already knows which project it is dealing with.

When to use it

Watch Time Entries hands you an entry and you want the full project behind it, for example to add its name to a line in your invoicing tool.

Watch out

it reads, it does not change anything. To find a project from a name instead of an ID, use Find Projects first.

Clockify10

Add a Project

Action

In Make“Adds a new project to a workspace.”

Creates a new project in the workspace you choose, so time can be logged against it straight away.

When to use it

a deal is marked won in your CRM or a quote is signed, and the matching Clockify project should exist before the team starts working.

Watch out

if the scenario runs twice for the same deal, you get two projects. A Find Projects step before it avoids the duplicate.

Clockify11

Delete a Project

Action

In Make“Deletes a project from a workspace.”

Removes a project from a workspace. Among all Clockify modules, this one deserves the most caution, since the project and its place in your reports go with it.

When to use it

test projects created while you built the scenario need cleaning up, or a deal was cancelled before any work was logged.

Watch out

consider this step irreversible. Test it on a throwaway project first, with Run once.

Task

3 modules

Clockify12

Add a Task

Action

In Make“Adds a new task to a project.”

Adds a task inside a project, the level where people pick what they are tracking time on.

When to use it

each new project should come with the same set of starter tasks, or a card created in your project board should become a trackable task in Clockify.

Watch out

a task always belongs to a project, so the scenario needs that project first, from Watch Projects, Find Projects or Add a Project.

Clockify13

Update a Task

Action

In Make“Updates an existing task.”

Edits a task that already exists, so Clockify reflects what changed in the tool where the work is actually planned.

When to use it

a card gets renamed in your project board and the matching Clockify task should follow, so people keep logging time on the right label.

Watch out

you need the exact task to edit. Pair it with Find Tasks when your scenario only knows the task name.

Clockify14

Find Tasks

In Make“Finds tasks by name in a project.”

Searches a project for tasks by name and hands back the matches as separate bundles.

When to use it

before adding a task, you want to check whether it already exists, or you need the real task so Run/Add a Time Entry can log hours against it.

Watch out

the search runs inside one project. If the scenario does not know the project yet, place Find Projects in front of it.

Client

3 modules

Clockify15

Find Clients

In Make“Finds clients by their name in a workspace.”

Looks for clients by name in a workspace. It is the bridge between the company name in your CRM and the client record in Clockify.

When to use it

an invoice or a contract arrives with a company name and you need to know whether that client already exists before creating anything.

Watch out

no result is a valid answer. Test the missing client case with Run once, so you know what your scenario does then.

Clockify16

Add a Client

Action

In Make“Adds a new client to a workspace.”

Creates a client in the workspace, the record your projects hang under in Clockify.

When to use it

a new customer signs in your CRM or accounting tool, and Clockify should get the same client so projects and hours can be grouped under it.

Watch out

nothing stops a second client with the same name. Put Find Clients first and only add when the search comes back empty.

Clockify17

Delete a Client

Action

In Make“Deletes an existing client.”

Deletes an existing client from Clockify. It is the counterpart of Add a Client, meant for cleanup rather than daily work.

When to use it

a duplicate client was created by an earlier run of your scenario, or a prospect record was added by mistake and never had any project.

Watch out

treat it as final. Test it on a dummy client first, and point it at one exact client, never at a long search result.

Tag

2 modules

Clockify18

Find Tags

In Make“Finds tags by name in a workspace.”

Searches the workspace for tags by name and returns the ones that match, so the scenario can attach the right label to an entry.

When to use it

you log time automatically and want to mark it as billable or tie it to a campaign, using a tag your team already created.

Watch out

spelling matters here. A tag named slightly differently will not come back, so check the bundles in Run once.

Clockify19

Add a Tag

Action

In Make“Adds a new tag to a workspace.”

Creates a new tag in the workspace, ready to be used on time entries by people or by your scenario.

When to use it

a new marketing campaign or cost center appears in another tool and should exist as a tag in Clockify before anyone logs time on it.

Watch out

if Watch Tags runs on the same workspace, your new tag starts that scenario too. Keep that in mind to avoid loops.

Workspace

2 modules

Clockify20

Find Workspaces

In Make“Finds workspaces for a currently logged-in user.”

Lists the workspaces the connected user can access. Most other Clockify modules ask for a workspace, and this is how the scenario picks one dynamically.

When to use it

you manage several Clockify workspaces, one per company or per client, and the scenario must choose the right one from incoming data.

Watch out

the answer depends on the account behind the API key. A missing workspace usually means that user has no access to it.

Clockify21

Add a Workspace

Action

In Make“Adds a new workspace.”

Creates a new Clockify workspace, the top-level space that holds projects, clients, tags and time entries.

When to use it

your agency spins up a separate workspace for each new entity or large account, and you want it created as part of the same onboarding scenario.

Watch out

a workspace is a big container. Run this step rarely and only after a clear event, never inside a loop.

Reports

4 modules

Clockify22

Get a Summary Report

Action

In Make“Retrieves a summary report.”

Pulls a summary report out of Clockify, the totals view rather than every line, and hands it to the next module.

When to use it

a project is marked finished and the client should get a clear total of the time spent, sent by email or saved in your shared drive.

Watch out

run it once with Run once and read the bundle before mapping anything, so you know what the report actually returns.

Clockify23

Get a Detailed Report

Action

In Make“Retrieves a detailed report.”

Retrieves a detailed report, the line-by-line version for when a total is not enough and someone wants to see each entry.

When to use it

finance asks for the hours behind an invoice, or a client disputes a total and you want the full breakdown sent without exporting it by hand.

Watch out

a detailed report can be large. Check what comes back in Run once, then only map what the next tool needs.

Clockify24

Get a Weekly Report

Action

In Make“Retrieves a weekly report.”

Returns the weekly report, the view that lays time out across the days of a week, straight into your scenario.

When to use it

a manager approves timesheets in another tool and needs the week view at hand when a team member submits their hours.

Watch out

this report reads data, it does not lock or approve anything. Approvals still happen wherever your team handles them.

Clockify25

Get an Expense Report

Action

In Make“Retrieves an expense report.”

Fetches the expense report from Clockify, so costs logged next to hours can travel to the tool that pays or bills them.

When to use it

a project closes and the expenses recorded on it must reach your accounting software or the invoice you are preparing for the client.

Watch out

the module only sees expenses people actually recorded in Clockify. An empty report usually means nothing was logged.

Groups

4 modules

Clockify26

Add a Group

ActionIn the docs only

Adds a group to Clockify. Make publishes no description for this module, so its name is the only clue to what it does, and this page will not guess the rest.

When to use it

you already work with groups in Clockify and want your scenario to create one instead of doing it by hand.

Watch out

since nothing is documented, build it once, click Run once and check in Clockify what it actually created before you switch the scenario on.

Clockify27

Update a Group

ActionIn the docs only

Updates a group that already exists in Clockify. Like Add a Group, it comes without an official description, so what it can change is something you discover in the editor, not here.

When to use it

a group you manage in Clockify needs a change and you want the scenario to apply it for you.

Watch out

it needs the right group. Run List Groups before it, then open the module fields to see what Make lets you edit.

Clockify28

List Groups

In Make“Retrieves a list of groups.”

Retrieves the groups of your Clockify account, each one as its own bundle the next modules can read.

When to use it

before Update a Group or Delete a Group, you want to pick the right group from the list rather than guess it.

Watch out

every module after it runs once per group, and each run counts as an operation. Keep only the modules you really need behind it.

Clockify29

Delete a Group

ActionIn the docs only

Deletes a group from Clockify. It has no official description either, so take the name as the whole promise and treat the removal as final.

When to use it

a group you set up in Clockify is no longer needed and you want the cleanup done by the scenario.

Watch out

test it on a throwaway group with Run once, and pick the target from List Groups rather than typing a name.

Other

1 module

Clockify30

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

The escape hatch: it calls any endpoint of the Clockify API using the connection you already set up, so there is no second login to manage.

When to use it

you need something the rest of the Clockify modules do not offer, and the Clockify API documentation shows an endpoint that does it.

Watch out

here you work closer to the API. Read the Clockify API documentation for the endpoint path and what it expects before running it.

Need help

Need help automating Clockify with Make?

A person reads every message.

FAQ

Clockify and Make: common questions

01Is the Clockify Make integration free?

Yes, Clockify is a standard app in Make, so it works from the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month, one per module run on one bundle. Your Clockify subscription is a separate matter.

02What does it take to connect Clockify to Make?

A Clockify account and its API key. In Clockify, open your Profile icon, then Profile Settings, scroll to the API section and click Generate. In Make, add a Clockify module, click Create a connection, paste the key into the API Key field and save. For a trigger, Make asks you to Create a webhook first, then the connection. The Make documentation lists no other prerequisite, and the connection is reused by all 36 Clockify modules.

03Do Clockify triggers react instantly in Make?

Yes. All 6 Clockify triggers are instant: Clockify calls Make through a webhook as soon as the event happens, whether a time entry changes, a timer starts or stops, or a project, task, client or tag is created. You do not need a 15 minute schedule for them. Each run still costs operations, and Watch Timers fires on both the start and the stop of a timer, so count two runs per timer session.

04What if a Clockify module is missing in Make?

Use Make an API Call. It can reach any endpoint of the Clockify API with the same connection, so you are not limited to the listed modules. The Make documentation points to the Clockify API documentation for the list of available endpoints, and that is where you check the path and what the call expects. Test the call with Run once and read the returned bundle before mapping it into the rest of the scenario.

05Make or n8n: which one fits Clockify?

It depends on the tool your team already builds in. Clockify is available in both: Make offers the 36 modules described on this page, including 6 instant triggers and a Make an API Call module, and n8n has its own Clockify node with a dedicated page on this site. Both rely on your Clockify account. Compare the specific triggers and actions you need on each side, then pick the tool where the rest of your automations already live.

Generate your API key in Clockify

Add a Clockify module in Make

Paste the key and save

Create the scenario

Set up Watch Projects

Add the task module

Test with Run once

Switch it on

Need help automating Clockify with Make?