Start free
TriggerStripeReal-timeUpdated June 2026

How do I trigger when a Stripe payment succeeds?

Short answer: Drop the "Stripe → Payment Succeeded" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Stripe, not on a polling schedule.

Use this triggerAll 10 Stripe triggers
Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder
Trigger
Payment Succeeded
When the matching event happens
when a payment is successfully completed in stripewatch for payment succeedednew payment succeededwhen payment succeededon payment succeeded
What this trigger returns
for the curious

You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "amount": 100,
  "status": "succeeded",
  "created": 1778804246,
  "currency": "usd",
  "customer": null,
  "event_id": "evt_xxx",
  "livemode": false,
  "event_type": "payment_intent.succeeded",
  "description": null,
  "occurred_at": 1778804246,
  "receipt_email": null,
  "payment_method": "pm_xxx",
  "amount_received": 100,
  "payment_intent_id": "pi_xxx"
}
Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

FieldTypeExample
amountnumber100
statusstring"succeeded"
creatednumber1778804246
currencystring"usd"
customernullnull
event_idstring"evt_xxx"
livemodebooleanfalse
event_typestring"payment_intent.succeeded"
descriptionnullnull
occurred_atnumber1778804246
receipt_emailnullnull
payment_methodstring"pm_xxx"
amount_receivednumber100
payment_intent_idstring"pi_xxx"
Pairs with

Drop these actions after Payment Succeeded.

Add Labels to Message
Gmail · Email
Add Reaction
Slack · Communication
Add Sheet Tab
Google Sheets · Spreadsheets & Databases
Create Company
HubSpot · CRM & Sales
FAQ

Questions about Payment Succeeded.

How does the Payment Succeeded trigger work in Stripe?
Fires when a payment is successfully completed in Stripe (payment_intent.succeeded). The standard post-charge hook for fulfillment, receipts, and revenue recognition.
Is the Payment Succeeded trigger real-time?
Yes. Payment Succeeded uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Stripe.
What data does Payment Succeeded return?
The full event payload from Stripe. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Payment Succeeded so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Stripe admin permissions to use Payment Succeeded?
For most Stripe accounts a standard user can authorize the trigger. Some Stripe plans require an admin to enable third-party webhooks. Check Stripe's docs if the trigger fails to register.
More triggers

Other Stripe triggers.

Trigger
Charge Failed
Fires when a charge attempt fails in Stripe (decline, fraud, insufficient funds). Use to alert the customer, retry, or kick off dunning.
Trigger
Checkout Completed
Fires when a Stripe Checkout session is completed (regardless of payment async status). Common use: provision the customer, send a receipt, or grant entitlements.
Trigger
New Customer
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.
Trigger
New Dispute
Fires when a charge dispute is created in Stripe (chargeback). Critical: route to ops immediately so you can gather evidence before the response window closes.
Trigger
Invoice Paid
Fires when an invoice is paid in Stripe. Use to recognise revenue in your accounting system, extend the subscription, or thank the customer.

Build a workflow on this trigger.

One trigger. 31+ downstream actions. Zero glue.

Try for freeRequest a demo