Skip to content
Per-pair page

Connect Clockify to Slack in two minutes.

Real-time triggers from Clockify, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Trigger app
Clockify as the trigger

Workflows fire when something happens in Clockify.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

ClockifySlack

When something happens in Clockify, do it in Slack.

3 Clockify triggers wired to 45 Slack actions. Most-used pairing: Time Entry CreatedRaw API Request.

SlackClockify

Or fire it the other way around.

13 Slack triggers wired to 3 Clockify actions downstream.

See SlackClockify
Popular pairings

Common Clockify → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
When time entry created in Clockify, raw api request in Slack.

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.

When time entry created in Clockify, add reaction in Slack.

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.

When time entry created in Clockify, archive channel in Slack.

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.

When time entry created in Clockify, cancel scheduled message in Slack.

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.

When timer started in Clockify, raw api request in Slack.

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.

When timer started in Clockify, add reaction in Slack.

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.

When timer started in Clockify, archive channel in Slack.

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.

When timer started in Clockify, cancel scheduled message in Slack.

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.

When timer stopped in Clockify, raw api request in Slack.

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".

How it works

Connect Clockify and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize Clockify and Slack

    Open Tiny Command, authorize Clockify and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick 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
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Raw API Request action below it. Map fields from the Clockify payload into the Slack inputs.

    slack.api-request
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Clockify + Slack.

How long does it take to connect Clockify and Slack on Tiny Command?
Under two minutes. Authorize Clockify and Slack once each, drop the Clockify trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Clockify ↔ Slack integration real-time?
Yes. Both Clockify and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between Clockify and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What Clockify events can trigger a Slack workflow?
Any of the 3 Clockify triggers, including "Time Entry Created". Each fires in real time when the matching event happens in Clockify.
Do I need a paid plan to use Clockify with Slack?
No. There's a free tier that covers most Clockify+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → Clockify instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/clockify page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Clockify.


Wire Clockify to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.