Per-pair page

Connect Stripe to GCP Cloud Functions in two minutes.

Real-time triggers from Stripe, ready-made actions in GCP Cloud Functions. Filter, transform, and route without writing a line of code.

Connect Stripe and GCP Cloud Functions See reverse direction

Trigger app

Stripe as the trigger

Workflows fire when something happens in Stripe.

See all 10 triggers →

Action app

GCP Cloud Functions as the action

Workflows do something in GCP Cloud Functions, instantly.

Call Cloud FunctionAPI
List Cloud FunctionsAPI

Both directions

Pick the way that fits your stack.

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

Stripe → GCP Cloud Functions

When something happens in Stripe, do it in GCP Cloud Functions.

10 Stripe triggers wired to 2 GCP Cloud Functions actions. Most-used pairing: Charge Failed → Call Cloud Function.

GCP Cloud Functions → Stripe

Or fire it the other way around.

0 GCP Cloud Functions triggers wired to 31 Stripe actions downstream.

Use any trigger in the catalog as the upstream.

See GCP Cloud Functions → Stripe →

Popular pairings

Common Stripe → GCP Cloud Functions workflows.

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

Showing 6 of 20 combinations

When charge failed in Stripe, call cloud function in GCP Cloud Functions.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When charge failed in Stripe, list cloud functions in GCP Cloud Functions.

Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.

When checkout completed in Stripe, call cloud function in GCP Cloud Functions.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When checkout completed in Stripe, list cloud functions in GCP Cloud Functions.

Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.

When new customer in Stripe, call cloud function in GCP Cloud Functions.

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.

When new customer in Stripe, list cloud functions in GCP Cloud Functions.

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.

How it works

Connect Stripe and GCP Cloud Functions in five steps.

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

1
Connect
Authorize Stripe and GCP Cloud Functions
Open Tiny Command, authorize Stripe and GCP Cloud Functions once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Stripe trigger
Drop the Stripe → Charge Failed trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/stripe.trigger-charge-failed
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 GCP Cloud Functions action
Drop the GCP Cloud Functions → Call Cloud Function action below it. Map fields from the Stripe payload into the GCP Cloud Functions inputs.
gcp-cloud-functions.call-function
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 Stripe + GCP Cloud Functions.

How long does it take to connect Stripe and GCP Cloud Functions on Tiny Command?

Under two minutes. Authorize Stripe and GCP Cloud Functions once each, drop the Stripe trigger and GCP Cloud Functions action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Stripe ↔ GCP Cloud Functions integration real-time?

Yes. Both Stripe and GCP Cloud Functions 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 Stripe and GCP Cloud Functions?

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 GCP Cloud Functions.

What Stripe events can trigger a GCP Cloud Functions workflow?

Any of the 10 Stripe triggers, including "Charge Failed". Each fires in real time when the matching event happens in Stripe.

Do I need a paid plan to use Stripe with GCP Cloud Functions?

No. There's a free tier that covers most Stripe+GCP Cloud Functions use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want GCP Cloud Functions → Stripe instead?

Build it the same way, in reverse. There's a dedicated /integrations/gcp-cloud-functions/with/stripe page with the reverse-direction triggers and actions.

Other apps that pair well with Stripe.

Stripe + Gmail

Stripe + Slack

Communication

Stripe + Google Sheets

Spreadsheets & Databases