Connect GCP Cloud Functions to Stripe in two minutes.
Real-time triggers from GCP Cloud Functions, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in GCP Cloud Functions.
- GCP Cloud Functions 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 GCP Cloud Functions, do it in Stripe.
0 GCP Cloud Functions triggers wired to 31 Stripe actions.
Or fire it the other way around.
10 Stripe triggers wired to 2 GCP Cloud Functions actions downstream.
See Stripe → GCP Cloud Functions →Common GCP Cloud Functions → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Connect GCP Cloud Functions and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize GCP Cloud Functions and Stripe
Open TinyCommand, authorize GCP Cloud Functions and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a GCP Cloud Functions trigger
Drop the GCP Cloud Functions → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/gcp-cloud-functions.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 GCP Cloud Functions 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.