Skip to content
Per-pair page

Connect Clockify to Stripe in two minutes.

Real-time triggers from Clockify, ready-made actions in Stripe. 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
Stripe as the action

Workflows do something in Stripe, instantly.

See all 31 actions →
Both directions

Pick the way that fits your stack.

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

ClockifyStripe

When something happens in Clockify, do it in Stripe.

3 Clockify triggers wired to 31 Stripe actions. Most-used pairing: Time Entry CreatedCancel Subscription.

StripeClockify

Or fire it the other way around.

10 Stripe triggers wired to 3 Clockify actions downstream.

See StripeClockify
Popular pairings

Common Clockify → Stripe workflows.

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

Showing 9 of 93 combinations
When time entry created in Clockify, cancel subscription in Stripe.

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, create charge in Stripe.

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, create checkout session in Stripe.

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, create coupon in Stripe.

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, cancel subscription in Stripe.

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, create charge in Stripe.

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, create checkout session in Stripe.

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, create coupon in Stripe.

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, cancel subscription in Stripe.

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 Stripe in five steps.

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

  1. 1
    Connect
    Authorize Clockify and Stripe

    Open Tiny Command, authorize Clockify and Stripe 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 Stripe action

    Drop the Stripe → Cancel Subscription action below it. Map fields from the Clockify payload into the Stripe inputs.

    stripe.cancel-subscription
  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 + Stripe.

How long does it take to connect Clockify and Stripe on Tiny Command?
Under two minutes. Authorize Clockify and Stripe once each, drop the Clockify trigger and Stripe action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the Clockify ↔ Stripe integration real-time?
Yes. Both Clockify and Stripe 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 Stripe?
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 Stripe.
What Clockify events can trigger a Stripe 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 Stripe?
No. There's a free tier that covers most Clockify+Stripe use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Stripe → Clockify instead?
Build it the same way, in reverse. There's a dedicated /integrations/stripe/with/clockify page with the reverse-direction triggers and actions.
Related

Other apps that pair well with Clockify.


Wire Clockify to Stripe in 2 minutes.

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