Resources · Make integration

Clockodo Make integrationAutomate Clockodo with Make.

Can Make keep your Clockodo customers, projects and entries in step with the rest of your tools? The Clockodo Make integration gives you 25 modules: 2 triggers, 15 actions and 8 searches. This page shows what they do, how to connect your account and how to build a first working scenario.

Try the Clockodo integration on Make See the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clockodo Make integration automate?

The Clockodo Make integration links your Clockodo account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Clockodo can start a scenario, receive data from other apps, or hand its records to them.

A project for every new customer. Watch new Customers spots a customer added in Clockodo, and Create a project opens the matching project right away, so nobody books hours against a missing project.

Entries that follow your other tools. Watch Entry fires as soon as an entry changes. From there, Get project and Get user fetch the context, and the next module in another app receives a clean record instead of a bare ID.

Reports without copy and paste. List entries, List entry groups and List services pull the records you need, one bundle (one item passed to the next module) at a time, ready for a spreadsheet or a message.

One honest limit: Make's own documentation for Clockodo is marked as limited, because little public information exists about the app. The module list is complete, but field details are thin, so test each module with real data first. For anything the listed modules skip, Make an API Call reaches the Clockodo API with the same connection. The same kind of flow can often be built in n8n too; the n8n vs Make comparison lays out the criteria. To go further, see Make training or, when a run fails, Make troubleshooting.

Connect

How do you connect Clockodo to Make?

01
Add a Clockodo module
Open a scenario, click the + and search for Clockodo. Pick any module, then click Create a connection. A connection is your Clockodo account linked to Make once and reused by every Clockodo module.
02
Name the connection
Give the connection a name you will recognize later, such as the account or team it belongs to. This step is optional, but it helps a lot once several people share the same Make organization.
03
Authorize and save
Make either opens the Clockodo authorization page or asks for the key Clockodo gives you. Follow the screen you get, then click Save. The module can now read your Clockodo data.

First scenario

Your first scenario: a Clockodo project for each new customer

GoalWhen a new customer appears in Clockodo, Make creates a project for that customer.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big + in the middle of the editor. That opens the list of apps you can use as the first module.
02
Add the trigger
Search for Clockodo, pick Watch new Customers and click Create a connection if you have none yet. This module starts the scenario whenever it finds a new customer.
03
Add the project action
Click the + on the right of the trigger and choose Create a project. Map the customer coming from the trigger into the module, so the new project is attached to the right customer.
04
Test with Run once
Add a test customer in Clockodo, then click Run once. Read the bundles each module received, then check that the project exists in Clockodo.
05
Schedule and switch on
Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Triggers

Which Clockodo events can start a scenario?

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

Clockodo1Watch Entry

Watch Entry

Instant trigger

In Make“Watches Entry updates”

Watch Entry starts your scenario the moment an entry is updated in Clockodo, so any follow-up (a message, a sheet row, a billing check) happens without anyone pressing a button.

How it fires

instant: the app calls Make through a webhook as soon as it happens. On the module you see the lightning badge, and no schedule is needed.

When to use it

when a change to an entry must reach another tool while it is still fresh, for example to keep a project dashboard current.

Watch out

it reacts to updates, so one entry edited several times can start several runs; plan for that in the next modules.

Clockodo2Watch new Customers

Watch new Customers

triggerIn the docs only

Watch new Customers hands your scenario each customer added in Clockodo since the last check, which makes it the natural starting point for onboarding flows built around a client.

How it fires

scheduled: Make checks the app on the scenario's schedule. The clock badge on the module sets that rhythm, every 15 minutes by default.

When to use it

when a new customer should open a project, a folder or a CRM record in another tool without manual entry.

Watch out

Make lists this module only in its documentation, with no description, and its scheduled type is inferred from its name, so confirm its behavior with Run once before building on it.

Modules

What else can Make do in Clockodo?

Clockodo gives you 23 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Clockodo1

Create a customer

Action

In Make“Creates a new customer.”

Create a customer adds a new client to Clockodo from data that lives elsewhere, so your team can start tracking hours for them without retyping anything.

When to use it

right after a deal is won in your CRM or a signup form is submitted.

Watch out

run List customer first if the same client might already exist, or you will end up with duplicates.

Clockodo2

Create a project

Action

In Make“Creates a new project.”

Create a project opens a project in Clockodo from your scenario, which saves someone from setting it up by hand every time work is sold.

When to use it

after Watch new Customers or Create a customer, so each client gets a project to log time against from the first day.

Watch out

map the customer carefully; a project attached to the wrong client is annoying to untangle later.

Clockodo3

Delete a project

Action

In Make“Deletes a project by id.”

Delete a project removes a Clockodo project by its ID. Your project list stays tidy when work gets cancelled upstream.

When to use it

when a deal is lost or an order is cancelled in another tool and the project was created automatically.

Watch out

a deletion cannot be undone from Make, so add a filter before this module and test on a dummy project first.

Clockodo4

Delete Customer

Action

In Make“Deletes a customer by id.”

Delete Customer erases a Clockodo customer by ID, useful when your client database is cleaned in another system and Clockodo should match it.

When to use it

when a test record or a duplicate customer created by an earlier scenario has to go.

Watch out

this is permanent, so fetch the customer with Get a customer first and check you are removing the right one before any live run.

Clockodo5

Edit project

Action

In Make“Edit the project by id.”

Edit project changes an existing Clockodo project found by its ID, so project details stay aligned with what your sales or planning tool says.

When to use it

when a project is renamed or its details change in another app and Clockodo should follow.

Watch out

you need the project ID; get it from List projects or from a previous module rather than typing it by hand.

Clockodo6

Get a customer

Action

In Make“gets a customer by id.”

Get a customer returns the full record of one Clockodo customer from its ID, turning a bare number coming from an entry or project into readable details.

When to use it

after Watch Entry, when the message or report you send needs the client's name rather than an ID.

Watch out

it reads one customer only; to browse all of them, List customer is the right module.

Clockodo7

Get entry

Action

In Make“Get specific entry by id.”

Get entry fetches one specific Clockodo entry by its ID, giving the next modules the complete record instead of a partial reference.

When to use it

when an ID reaches your scenario from another app or a webhook, and you need the whole entry before acting on it.

Watch out

it only works with a valid ID, so map it from a previous module instead of typing a value you copied from the app.

Clockodo8

Get lumpsum service

Action

In Make“Get a specific lumpsumservices by id.”

Get lumpsum service reads one lump sum service from Clockodo by its ID, so a billing flow can pick up its details without a manual lookup.

When to use it

when an invoice or quote built in another tool has to show a flat fee service defined in Clockodo.

Watch out

to find the right ID in the first place, run List lumpsum services once and note it down.

Clockodo9

Get project

Action

In Make“Get a specific project by an given id.”

Get project returns a single Clockodo project from its ID, which adds the project context to anything else your scenario sends out.

When to use it

after Watch Entry, to show which project the updated entry belongs to in a Slack message or a sheet.

Watch out

Clockodo also exposes Get project v4; pick one and stick to it in a scenario so the mapped data stays consistent.

Clockodo10

Get running clock

Action

In Make“Retrieve the current running entry.”

Get running clock tells your scenario which entry is currently running in Clockodo, so you can react to live work instead of finished entries only.

When to use it

to post who is on which task in a team channel, or to check that a timer is running before a meeting starts.

Watch out

test it once while no timer runs, and read what Run once shows, so the next modules handle that case.

Clockodo11

Get user

Action

In Make“Get a specific user by id.”

Get user loads one Clockodo user by ID, turning the user reference found on an entry into a name and details other tools understand.

When to use it

when a notification or report must say who logged the time, not just show a number.

Watch out

it needs the exact ID; when you only know a name, start from List users and filter the result.

Clockodo12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends any request to the Clockodo API with the connection you already set up, covering what the other listed modules leave out.

When to use it

when you need a Clockodo feature that has no dedicated module, such as an object Make does not list.

Watch out

you write the address and content of the request yourself, so keep the Clockodo API documentation open and test the call with Run once.

Clockodo13

Update Customer

Action

In Make“Update a specific customer.”

Update Customer rewrites the details of an existing Clockodo customer, so a change made in your CRM does not leave an outdated record in time tracking.

When to use it

when a client changes its name or details in the tool your sales team uses, and Clockodo should mirror it.

Watch out

fields you map empty may overwrite existing values; map only what actually changed.

Clockodo14

Update entry

Action

In Make“Update a specific entry by id.”

Update entry corrects a specific Clockodo entry by ID from inside a scenario, which saves someone from fixing records one by one in the app.

When to use it

when an approval or a correction happens in another tool and the entry in Clockodo has to reflect it.

Watch out

never pair it with Watch Entry on the same entry without a filter, or each update starts the scenario again.

Clockodo15

List customer

In Make“List all customers.”

List customer returns every Clockodo customer, one bundle each, so later modules can process them one after another or check whether a client exists.

When to use it

before Create a customer, to look for an existing record and avoid a duplicate, or to export your client list.

Watch out

each customer that flows into the next module costs operations, so filter early.

Clockodo16

List entries

In Make“List all entries by given criterion.”

List entries pulls the Clockodo entries that match the criteria you set, giving you the raw material for a timesheet export or a billing check.

When to use it

when a report, an invoice draft or a sheet should be filled from logged time rather than typed.

Watch out

a broad criterion can return many bundles; narrow it and add an aggregator if the destination expects one file.

Clockodo17

List entries texts

In Make“List all entries by given criterion.”

List entries texts returns the texts attached to Clockodo entries matching your criteria, handy when the descriptions matter more than the hours.

When to use it

to build a summary of what was done on a project for a client update, based on what people wrote.

Watch out

Make describes it with the same line as List entries, so run it once to see exactly what it returns.

Clockodo18

List entry groups

In Make“List entrygroups for reportings.”

List entry groups is the module Make describes as built for reporting: expect your entries grouped rather than one long list of lines.

When to use it

when a dashboard or a management sheet needs grouped figures for reporting rather than every single line.

Watch out

the grouping options are not detailed in Make's documentation, so compare the output with a Clockodo report first.

Clockodo19

List lumpsum services

In Make“List all lumpsumservice.”

List lumpsum services returns all the lump sum services defined in Clockodo, which gives you a quick way to find their IDs or sync them into a catalog.

When to use it

to keep a price list in a spreadsheet or quoting tool aligned with the flat fee services in Clockodo.

Watch out

each service arrives as its own bundle, so aggregate them if you want a single row or message.

Clockodo20

List projects

In Make“List all projects.”

List projects returns every Clockodo project as separate bundles, a good base for syncing projects to a planning tool or looking one up by name.

When to use it

before Create a project, to check the project does not already exist, or to build a project overview in another app.

Watch out

on a large account, add a filter right after it to keep the operation count down.

Clockodo21

List services

In Make“Lists all services.”

List services brings back all the services set up in Clockodo, the kinds of work people book their hours against, so other tools can reuse the same list.

When to use it

when a form or a planning sheet should offer exactly the services your team tracks in Clockodo.

Watch out

lump sum services have their own module, List lumpsum services, so check which of the two lists you actually need.

Clockodo22

List users

In Make“List all user.”

List users returns every user of your Clockodo account, one bundle each, so you can match people across tools or check who has access.

When to use it

to keep a team directory in sync, or to find the ID a module such as Get user needs.

Watch out

it is also the simplest read to test a fresh connection with Run once before building anything bigger.

Clockodo23

Get project v4

ActionIn the docs only

Get project v4 is a second way to read one Clockodo project, listed by Make without any official description, which is why it deserves a quick test before use.

When to use it

when Get project does not return what you expect and you want to compare both outputs on the same project.

Watch out

since Make gives no description for it, rely on what Run once shows rather than on assumptions.

Need help

Need help automating Clockodo with Make?

A person reads every message.

FAQ

Clockodo and Make: common questions

01Is the Clockodo Make integration free?

Yes, Clockodo is a standard app in Make, so you can use it on the Free plan. That plan has real limits: 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Clockodo subscription is a separate matter, handled on the Clockodo side.

02What do you need to connect Clockodo to Make?

A Clockodo account and a Make account are enough to start. Make's documentation lists no special prerequisite and no official connection steps for Clockodo, so you follow the generic path: add a Clockodo module, click Create a connection, optionally name it, authorize Make on the Clockodo page or paste the key Clockodo gives you, then save. Test the connection with a simple read module such as List users and Run once.

03Does the Clockodo trigger in Make work in real time?

It depends on the trigger. Watch Entry is instant: Clockodo calls Make through a webhook as soon as an entry is updated, so the scenario starts right away. Watch new Customers is scheduled: Make checks Clockodo on the scenario's schedule, every 15 minutes by default, and no faster than every 15 minutes on the Free plan. On a paid plan the interval can go down to 1 minute. Pick the trigger that matches how fast the next step really needs to happen.

04What if a Clockodo module is missing in Make?

Use Make an API Call. It sends any request to the Clockodo API with the connection you already created, so you are not limited to the 25 listed modules. Keep in mind that Make's own documentation for Clockodo is marked as limited because little public information exists about the app, so field details are sparse. Test each call with Run once and read the returned bundles before switching the scenario on.

05Should you use Make or n8n for Clockodo?

It depends on the tool your team already works in. On the Make side, Clockodo comes with 25 modules, including an instant trigger on entries and Make an API Call for anything else, all usable without code. The same kind of app often has an n8n node too, so check both catalogs for the exact actions you need. Choose the one whose editor you and your colleagues will actually maintain over time.

Add a Clockodo module

Name the connection

Authorize and save

Create the scenario

Add the trigger

Add the project action

Test with Run once

Schedule and switch on

Need help automating Clockodo with Make?