Connect Clockify to Notion in two minutes.
Real-time triggers from Clockify, ready-made actions in Notion. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Clockify.
- Time Entry CreatedWebhook
- Timer StartedWebhook
- Timer StoppedWebhook
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Clockify, do it in Notion.
3 Clockify triggers wired to 12 Notion actions. Most-used pairing: Time Entry Created → Append Content.
Or fire it the other way around.
3 Notion triggers wired to 3 Clockify actions downstream.
See Notion → Clockify →Common Clockify → Notion workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
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 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 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 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 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 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 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".
Connect Clockify and Notion in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Clockify and Notion
Open Tiny Command, authorize Clockify and Notion once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Clockify trigger
Drop the Clockify → Time Entry Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/clockify.trigger-time-entry-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Notion action
Drop the Notion → Append Content action below it. Map fields from the Clockify payload into the Notion inputs.
notion.append-blocks - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Clockify + Notion.
How long does it take to connect Clockify and Notion on Tiny Command?
Is the Clockify ↔ Notion integration real-time?
Can I filter or transform data between Clockify and Notion?
What Clockify events can trigger a Notion workflow?
Do I need a paid plan to use Clockify with Notion?
What if I want Notion → Clockify instead?
Other apps that pair well with Clockify.
Wire Clockify to Notion in 2 minutes.
Free tier available. No credit card. No onboarding call.
