See subscription context for a Bugsnag incident
Include a customer's Stripe subscription records in the same report as a billing related error.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List subscriptions
Retrieves a list of stripe subscriptions, optionally filtered by various criteria such as customer, price, status, collection method, and date ranges, with support for pagination.
Why this helps
When subscription state is relevant to an incident, looking it up by hand adds delay and creates more context switching.
- Retrieve subscription information for a specified Stripe customer.
- Help distinguish subscription context from application error symptoms.
- Make missing customer identifiers visible instead of guessing.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Stripe once in the Notis portal.
- 2Create an automation named Subscription Incident Context.
- 3Tell Notis to list subscriptions for the Stripe customer ID in a Bugsnag alert and summarize returned statuses, reporting if the customer ID is missing.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real alert that includes a Stripe customer ID.
Questions about this workflow
Does this cancel or change a subscription?
No. It lists subscriptions for review.
Can it tell which subscription caused the error?
Only if the incident provides enough context to identify it. The workflow should present returned subscription information without claiming an unsupported causal link.
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.