Skip to content
ClickRuntime

Automate Clockify

Use Clockify data the moment it matters: see who is short on hours by Friday, post the day's tracked time per person and project to your team, get notified as new entries come in, and know when a project eats into its time estimate. Describe the result to your assistant, check its plan, then leave it to run against your workspace.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every Friday at 3pm, email me which Clockify users have logged under 35 hours this week and how many hours each one has.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Clockify

Short-week warnings before timesheets close, a daily team time post, live notice of new entries and alerts on projects running past their estimate. These are ready-made starting points. Anything else you can describe works too.
On a schedule

See who is short on hours before the week ends

Each Friday afternoon you get the names of people who tracked fewer hours than your target, while there is still time to fix it.

See how it works
On a schedule

Post today's tracked time to your team channel

Every weekday evening your channel gets the hours each person tracked today, split by project.

See how it works
The moment it happens

Get an email as soon as time is logged

Each new entry in your workspace reaches you with the person, project and duration.

See how it works
On a schedule

Know when a project nears its time estimate

You get one email when a project passes 80% of its estimate and another if it goes past 100%.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Clockify, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Clockify automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Clockify should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every day at 6pm, find Clockify time entries without a project or description and send me the list so I can fix them.

Every Monday, send each team member a Slack DM with their Clockify hours from last week broken down by project.

At the end of each month, pull Clockify billable hours per client, write them to a Google Sheet, and email each client a summary.

Beyond chat

Have Clockify work when you're not in the chat

Connecting Clockify to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Clockify

Clockify connects with an API key you generate from your own profile.

Clockify

Time tracking

  1. In Clockify, open Profile Settings and go to the API section.
  2. Click Generate to create a key. If your workspace uses its own subdomain, generate the key while signed in on that subdomain.
  3. In the ClickRuntime dashboard, open Connections & secrets and save the key as a Clockify secret.

Good to know

Clockify limits that affect automations

  • What a key can see depends on your role: team-wide reports and every project need an admin (or a project manager for their projects), and creating webhooks needs an admin.
  • A workspace on a custom subdomain needs a key generated on that subdomain.
  • Workspaces hosted in a regional data center use that region's API address, so make sure your connection matches your region.
  • A new-entry webhook fires for every entry, which can get noisy on a big team. Collecting entries and sending them as one digest is often better.

FAQ

Questions about automating Clockify

What can ClickRuntime see in Clockify?
What your API key's user can see: time entries, users, projects with their estimates, and summary reports. With an admin key that covers the whole workspace.
Can it react as soon as someone logs time?
Yes. Clockify can send a webhook for each new time entry, and an admin key is needed to set that up. On busy workspaces you may prefer a daily round-up.
Does the estimate alert work on the free plan?
Yes. It reads each project's estimate and tracked time through the API and emails you when a project passes 80% or 100%, which helps if your plan has no built-in alerts. Projects without an estimate are skipped.
Will I be emailed about the same project every morning?
No. The automation remembers which thresholds it has already reported, so you only hear when a project crosses a new one.
Do these automations need AI?
No, they total and compare hours. Should you add a written summary, the AI is part of every ClickRuntime plan and you don't supply a key.
Is this a Clockify connector for ChatGPT or Claude?
Not for chatting with Clockify data. A chat connector lets your assistant read and change Clockify while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Clockify event.

Related pages

Keep exploring

Tell your assistant what Clockify should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude