Connect Gumlet to Stripe in two minutes.
Real-time triggers from Gumlet, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Gumlet.
- Gumlet has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.
Workflows do something in Stripe, instantly.
- Cancel SubscriptionAPI
- Create ChargeAPI
- Create Checkout SessionAPI
- Create CouponAPI
- Create CustomerAPI
- Create Payment IntentAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Gumlet, do it in Stripe.
0 Gumlet triggers wired to 31 Stripe actions.
Or fire it the other way around.
10 Stripe triggers wired to 3 Gumlet actions downstream.
See Stripe → Gumlet →Common Gumlet → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Connect Gumlet and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Gumlet and Stripe
Open TinyCommand, authorize Gumlet and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Gumlet trigger
Drop the Gumlet → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/gumlet.event - 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 Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the Gumlet payload into the Stripe inputs.
stripe.cancel-subscription - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.