Per-pair page

ClickUp + Stripe: revenue events into actionable tasks.

Create ClickUp tasks from Stripe events that need human attention — failed charges, disputes, large refunds, new high-value customers. Critical finance ops without a separate queue.

Connect ClickUp and Stripe See reverse direction

Trigger app

ClickUp as the trigger

Workflows fire when something happens in ClickUp.

See all 6 triggers →

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.

ClickUp → Stripe

When something happens in ClickUp, do it in Stripe.

6 ClickUp triggers wired to 31 Stripe actions. Most-used pairing: Comment Posted → Cancel Subscription.

Stripe → ClickUp

Or fire it the other way around.

10 Stripe triggers wired to 9 ClickUp actions downstream.

See Stripe → ClickUp →

Popular pairings

Common ClickUp → Stripe workflows.

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

Showing 9 of 186 combinations

When comment posted in ClickUp, cancel subscription in Stripe.

Fires when a new comment is posted on a task in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. Use to mirror discussion to Slack or feed AI summaries.

When comment posted in ClickUp, create charge in Stripe.

When comment posted in ClickUp, create checkout session in Stripe.

When comment posted in ClickUp, create coupon in Stripe.

When new list in ClickUp, cancel subscription in Stripe.

Fires when a new list is created in the selected ClickUp space. The webhook is registered automatically when the workflow is published. Useful for templated list provisioning or governance audit logs.

When new list in ClickUp, create charge in Stripe.

When new list in ClickUp, create checkout session in Stripe.

When new list in ClickUp, create coupon in Stripe.

When new task in ClickUp, cancel subscription in Stripe.

Fires when a new task is created in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. The standard inbound hook for routing, enrichment, and notification flows.

How it works

Connect ClickUp and Stripe in five steps.

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

1
Connect
Authorize ClickUp and Stripe
Open Tiny Command, authorize ClickUp and Stripe once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a ClickUp trigger
Drop the ClickUp → Comment Posted trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/clickup.trigger-comment-posted
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
Action
Add the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the ClickUp payload into the Stripe inputs.
stripe.cancel-subscription
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 ClickUp + Stripe.

What Stripe events should fire ClickUp tasks?

Five focus areas: dispute.created, large refunds, repeated charge.failed for the same customer, subscription.created for enterprise tier, subscription.deleted for high-MRR customers.

How do I create a ClickUp task for every Stripe dispute?

Stripe Dispute Created → ClickUp Create Task in a "Disputes" list, assigned to the ops lead, due date = dispute deadline. Add Stripe charge ID and amount in custom fields.

Can I create different ClickUp tasks for different Stripe subscription tiers?

Yes. Switch on subscription price ID. Enterprise → "Enterprise Onboarding" list. Pro → "Pro Welcome Sequence" list. Free → no task. One trigger, many downstream branches.

How do I close the loop — close the ClickUp task when Stripe data updates?

Stripe Dispute Updated where status = "won" → look up the linked ClickUp task ID → Update Task with status = "complete". Team sees only open work.

Can I add Stripe customer details to the ClickUp task?

Yes. Stripe Get Customer between trigger and Create Task. Pass email, name, MRR, plan into ClickUp task description or custom fields. Ops sees the context at a glance.

How do I prevent creating ClickUp tasks for test-mode Stripe events?

Filter the trigger on livemode = true. Stripe webhooks include this flag; test events have livemode: false. Otherwise local dev work spams your team's ClickUp.

Other apps that pair well with ClickUp.

ClickUp + Gmail

ClickUp + Slack

Communication

ClickUp + Google Sheets

Spreadsheets & Databases