🇬🇧 EN

💳 Stripe Trigger

The Stripe Trigger fires a workflow when Stripe sends a webhook event to your Flusso endpoint. It automatically validates Stripe's webhook signature so you can be certain that every event genuinely came from Stripe — not from a spoofed request. Common use cases include reacting to successful payments, subscription changes, and invoice events.

Category: Triggers · Type identifier: stripe_trigger

Overview

Stripe uses webhooks to notify your applications of events that happen in your Stripe account: a customer's payment succeeded, a subscription was cancelled, an invoice became overdue. The Stripe Trigger makes it easy to respond to these events in Flusso without writing any code.

Unlike the generic Webhook Trigger, the Stripe Trigger handles Stripe-specific signature validation automatically. Stripe signs every webhook payload with your webhook signing secret (using HMAC-SHA256 and a timestamp to prevent replay attacks), and Flusso verifies that signature before firing the workflow. If the signature is invalid, the request is rejected and the workflow does not run.

You can optionally filter the trigger to only fire for specific Stripe event types — for example, only payment_intent.succeeded — by entering event type names in the Event Types field. Leave it blank to accept all Stripe events and use a Switch node downstream to route different event types to different logic.

Configuration

Field	Required	Description
Webhook Secret	Required	The webhook signing secret from your Stripe Dashboard. This is the `whsec_…` value shown under Developers → Webhooks → [your webhook endpoint] → Signing secret. Flusso uses this to verify every incoming request came from Stripe.
Event Types	Optional	A comma-separated list of Stripe event types that this trigger accepts. For example: `payment_intent.succeeded, customer.subscription.deleted`. If left blank, the trigger fires for all event types that Stripe sends to this endpoint.

Finding your Stripe Webhook Secret

Log in to your Stripe Dashboard at dashboard.stripe.com.
Go to Developers → Webhooks in the left sidebar.
Click "Add endpoint" and enter your Flusso workflow's webhook URL. You can find this URL in the Stripe Trigger's configuration drawer in Flusso.
Select the events you want Stripe to send. You can select all events or specific ones.
After saving, click "Reveal" next to "Signing secret". Copy the whsec_… value and paste it into the Webhook Secret field in Flusso.

Output Data

Variable	Type	Description
`trigger.output.payload`	Object	The full Stripe event object, including the `data.object` field that contains the event's subject (e.g. the PaymentIntent or Subscription object).
`trigger.output.event_type`	String	The Stripe event type string, e.g. `payment_intent.succeeded`, `customer.subscription.deleted`.
`trigger.output.headers`	Object	The HTTP request headers from Stripe, including the `stripe-signature` header used for validation.

// Access the event type {{ trigger.output.event_type }} // Access the Stripe object (e.g. a PaymentIntent) {{ trigger.output.payload.data.object.id }} {{ trigger.output.payload.data.object.amount }} {{ trigger.output.payload.data.object.currency }} // Access customer email from a charge event {{ trigger.output.payload.data.object.billing_details.email }}

Example Usage

Send a thank-you email on successful payment

Add a Stripe Trigger. Enter your webhook signing secret and set Event Types to payment_intent.succeeded.
Add an HTTP Request node to look up the customer's email address from your database or from the Stripe API using {{ trigger.output.payload.data.object.customer }}.
Add an Email Notification node. Set the recipient to the customer's email and include the payment amount in the body:
Thank you for your payment of ${{ trigger.output.payload.data.object.amount_received }}!

Tips & Notes

Keep your webhook secret secure. The webhook signing secret is a sensitive credential. Never share it, commit it to source control, or display it in logs. If it is ever exposed, immediately rotate it in the Stripe Dashboard and update the value in Flusso.

Stripe uses test and live mode webhooks separately. Your test mode webhook has a different signing secret than your live mode webhook. Make sure you are using the correct secret for the environment you are testing or running in production.
Stripe retries failed deliveries. If Flusso does not return a 200 response quickly (for example, because the workflow takes a long time to start), Stripe will retry the webhook. Flusso's idempotency handling prevents duplicate runs for the same event, but be aware of Stripe's retry behaviour when designing your workflow.
Use the Stripe CLI for local testing. During development, you can use the Stripe CLI to forward real Stripe events to a local Flusso instance: stripe listen --forward-to localhost/api/webhooks/{id}.

Related Nodes

Webhook Trigger — generic webhook trigger for any HTTP POST source.
GitHub Trigger — webhook trigger with built-in GitHub HMAC validation.
Shopify Trigger — webhook trigger with built-in Shopify HMAC validation.