Stripe Trigger
Starts the workflow on Stripe events such as a successful payment, a completed checkout or a new subscription. Buni.ai registers the webhook in Stripe for you.
The Stripe Trigger starts your workflow when something happens in your Stripe account: a payment succeeds, a checkout completes, a subscription changes. You pick the events; Buni.ai registers the webhook in Stripe and checks every delivery's signature.
Where you find it
Drag Stripe Trigger from the Triggers group of an automation project's node palette. A workflow can have several triggers; each one starts the workflow from its own output.
When to use it
- Send a receipt or unlock access when a payment succeeds.
- Follow up on failed payments or cancelled subscriptions.
Before you start
Add a Stripe connection with your account's Secret Key (sk_live_… or sk_test_…) in the project's Integrations tab. See Credentials and connections.
Settings
The panel header has an Enabled / Paused switch. New triggers start Enabled; a paused trigger shows Paused on its canvas card and starts no runs.
Prop
Type
| Event | Stripe event |
|---|---|
| Payment succeeded | payment_intent.succeeded |
| Payment failed | payment_intent.payment_failed |
| Checkout completed | checkout.session.completed |
| Customer created | customer.created |
| Customer updated | customer.updated |
| Subscription created | customer.subscription.created |
| Subscription updated | customer.subscription.updated |
| Subscription paused | customer.subscription.paused |
| Subscription resumed | customer.subscription.resumed |
| Subscription cancelled | customer.subscription.deleted |
| Invoice paid | invoice.paid |
| Invoice payment failed | invoice.payment_failed |
Once the trigger has a connection and at least one event, saving the workflow registers the Test URL with Stripe, and publishing registers the Prod URL. There is nothing to paste into Stripe.
Leave the signing secret alone
Buni.ai stores the signing secret Stripe issues and checks every delivery with it, even though the Endpoint section still shows Unverified. Do not select Generate signing secret on this trigger: a generated secret replaces Stripe's, and deliveries fail verification.
Send test event takes a Sample payload and shows what the trigger would pass to the workflow, without running the workflow's nodes. Recent deliveries lists the latest runs this trigger started, newest first, with their status and duration.
Outputs
| Field | Contains |
|---|---|
input.payload | The whole Stripe event, for example input.payload.data.object.amount. |
input.event | The Stripe event type, such as payment_intent.succeeded. |
{{state.trigger.type}} is WEBHOOK.
Tips and limits
- Stripe can deliver an event more than once; each Stripe event starts at most one run.
- Events you did not select are acknowledged and ignored.
- Removing the trigger stops it from starting runs but leaves the webhook endpoint in your Stripe account. Delete it in your Stripe Dashboard's webhook settings.
Related
Error Trigger
Starts the workflow when another run in the same project fails, with the failure's details, so one handler can alert your team.
GitHub Trigger
Starts the workflow on GitHub events in one repository: pushes, pull requests, issues, comments, releases and workflow runs. Buni.ai registers the webhook for you.