Clockify
Clockify time-entry and timer events
Clockify is the freemium leader in team time tracking, and Tiny Command surfaces three triggers that capture the timer lifecycle: Time Entry Created (fires for manually added entries — the "I forgot to start the timer" backfill), Timer Started (an active in-progress timer began), and Timer Stopped (the timer stopped, which is the standard event for billing and project-rollup workflows). Three actions cover the writes and reads: Create Time Entry (post a duration-based entry programmatically, useful for converting calendar meetings into tracked time), List Workspaces, and List Projects. The connection uses a per-user API key from the Clockify profile page. Every entry belongs to a workspace and optionally to a project, task, and tag set — Timer Stopped's payload includes all of these plus billable flag and the elapsed duration. The typical workflow: when Timer Stopped fires for a billable entry on a client project, fan out to invoicing (QuickBooks or HoneyBook), to the team's daily-summary Slack thread, and to a Notion timesheet database.
Workflows start when Clockify does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
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.
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".
Do anything Clockify can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Time Entry | Posts a duration-based entry with project, task, tags, billable flag. Useful for "calendar meeting marked as billable → auto-log time in Clockify" or for batch-importing time from external sources. |
| List Projects | Returns every project in a workspace with client, hourly rate, billable settings. Useful for resolving project IDs at workflow-build time and for "project utilisation" reporting workflows that aggregate by project. |
| List Workspaces | Returns every workspace the connected user is a member of. Multi-workspace users (agencies tracking time across client workspaces) configure one Tiny Command connection per workspace they want to track. |
Pre-built Clockify workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Clockify once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Clockify field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Clockify integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Clockify to Tiny Command?
What Clockify triggers does Tiny Command support?
What Clockify actions can I run from a workflow?
Is the Clockify integration real-time?
Do I need to write code to use Clockify with Tiny Command?
How much does the Clockify integration cost?
More other apps people connect.
Same category as Clockify, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Clockify.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
