Connect Stripe to Cal.com in two minutes.
Real-time triggers from Stripe, ready-made actions in Cal.com. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Stripe.
- Charge FailedWebhook
- Checkout CompletedWebhook
- New CustomerWebhook
- New DisputeWebhook
- Invoice PaidWebhook
Workflows do something in Cal.com, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Stripe, do it in Cal.com.
10 Stripe triggers wired to 7 Cal.com actions. Most-used pairing: Charge Failed → Cancel Booking.
Or fire it the other way around.
3 Cal.com triggers wired to 31 Stripe actions downstream.
See Cal.com → Stripe →Common Stripe → Cal.com workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Fires when a new customer is created in Stripe. Use to mirror to your CRM, send a welcome email, or enrich the customer record before first charge.
Connect Stripe and Cal.com in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Stripe and Cal.com
Open TinyCommand, authorize Stripe and Cal.com once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Stripe trigger
Drop the Stripe → Charge Failed trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/stripe.trigger-charge-failed - 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 Cal.com action
Drop the Cal.com → Cancel Booking action below it. Map fields from the Stripe payload into the Cal.com inputs.
cal-com.cancel-booking - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.
