TriggerClockifyReal-timeUpdated May 2026
When does Clockify fire on timer stop?
Short answer: Drop the "Clockify → Timer Stopped" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Clockify, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Timer Stopped
When the matching event happens
when a timer is stopped in clockifynew timer stoppedwhen timer stoppedwatch for timer stoppedon timer stopped
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"id": "te_123","project": "proj_123","description": "Working on feature"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | string | "te_123" |
| project | string | "proj_123" |
| description | string | "Working on feature" |
Pairs with
Drop these actions after Timer Stopped.
FAQ
Questions about Timer Stopped.
How does the Timer Stopped trigger work in Clockify?
Fires when a running timer stops — the canonical event for billing and rollup workflows since it carries the full elapsed duration. The standard hook for "billable entry stopped → push to invoicing, log to project rollup, notify the client retainer dashboard".
Is the Timer Stopped trigger real-time?
Yes. Timer Stopped uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Clockify.
What data does Timer Stopped return?
The full event payload from Clockify. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Timer Stopped so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Clockify admin permissions to use Timer Stopped?
For most Clockify accounts a standard user can authorize the trigger. Some Clockify plans require an admin to enable third-party webhooks. Check Clockify's docs if the trigger fails to register.
More triggers
Other Clockify triggers.
Trigger
Time Entry Created
Fires when a time entry is added — typically the "I forgot to start the timer" backfill case where someone types in duration after the fact. Useful for billing-trigger workflows and for time-tracking-completeness audits.
TriggerTimer Started
Fires when a running timer begins. Useful for presence-aware workflows ("Sarah just started working on Project X → mark her as busy in Slack") or for capacity dashboards showing who's on what.
Build a workflow on this trigger.
One trigger. 3+ downstream actions. Zero glue.
