Stripe Trigger
The Stripe Trigger starts your workflow the moment Stripe sends a webhook event — a successful payment, a completed checkout, a paid invoice, a canceled subscription, or any other Stripe event type you choose.
Payment Automation: Point a Stripe webhook endpoint at your workflow and react to payments, checkouts, and subscription changes in real time.
Key Features
- Real-Time Webhooks: Your workflow fires the instant Stripe delivers the event
- Any Stripe Event: Pick from common events or add any event type Stripe supports
- Signature Verification: Optionally verify the
stripe-signatureheader with your endpoint's webhook signing secret - Event Filtering: Only the event types you select start the workflow — everything else is ignored
Common Events
| Event | Description |
|---|---|
payment_intent.succeeded | Fires when a payment completes successfully (default) |
checkout.session.completed | Fires when a Checkout session finishes |
invoice.paid | Fires when an invoice is paid |
customer.subscription.deleted | Fires when a subscription is canceled |
You can also type any other Stripe event (e.g. charge.refunded, customer.created) into the "Other events" field. Leave everything empty to receive all events.
Configuration
| Parameter | Type | Required | Description |
|---|---|---|---|
| Events | Multi-select + free text | No | Event types to listen for (defaults to payment_intent.succeeded; empty = all events) |
| Webhook signing secret | Secret | No | The endpoint's whsec_... secret from the Stripe Dashboard. Strongly recommended — without it, incoming events are not verified |
Setting up the webhook in Stripe
- Add the Stripe Trigger block to your workflow and copy the Webhook URL shown in its settings (
https://<your-builder>/api/webhooks/stripe/<workflowId>). - Publish the workflow — events are only delivered to published, active workflows.
- In the Stripe Dashboard, open Developers → Webhooks → Add endpoint.
- Paste the Webhook URL as the endpoint URL.
- Select the events you want to send (match them with the events selected on the trigger block).
- Create the endpoint, then open it and click Reveal under Signing secret. Copy the
whsec_...value. - Paste the signing secret into the trigger block's Webhook signing secret field so Indite can verify that events really come from Stripe.
⚠️
The webhook signing secret is not your Stripe API key. Each webhook endpoint has its own signing secret, shown on the endpoint's detail page.
Output
Downstream blocks can reference the trigger's output:
| Field | Description |
|---|---|
event | The Stripe event type (e.g. payment_intent.succeeded) |
id | The Stripe event id (evt_...) |
data | The event's primary object (e.g. the PaymentIntent or Checkout Session) |
raw | The full webhook payload |