Review the payment intent tied to a Bugsnag alert
Bring the Stripe payment intent into the same run report as the error that needs attention.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve payment intent
Retrieves a paymentintent by its id; `client secret` is required if a publishable api key is used.
Why this helps
An error stack alone may not explain what happened to the payment, leaving founders to piece together intent status manually.
- See the current payment intent details alongside an error alert.
- Reduce manual searching during payment investigations.
- Surface missing or ambiguous payment intent IDs in the report.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Stripe once in the Notis portal.
- 2Create an automation named Payment Intent Error Review.
- 3Tell Notis to retrieve the payment intent identified in a Bugsnag alert and summarize the returned status, reporting if the ID is absent.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real alert containing a Stripe payment intent ID.
Questions about this workflow
Can it confirm or retry the payment?
No. This workflow retrieves the payment intent for review and does not change or confirm it.
What if the alert has no payment intent ID?
The instruction should have Notis report that the identifier is missing rather than guess which payment intent is involved.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to Stripe. A trigger fires from one place; an action lands in another.
Bugsnag triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Bugsnag and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.