Check the Stripe customer connected to an incident
Give your incident review the Stripe customer context it needs without a separate lookup.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Incident responders may know a customer is affected but lack the billing context to follow up confidently.
- Retrieve the specific customer record named in an incident.
- Keep customer context with the incident run report.
- Avoid broad customer searches when an exact ID is available.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Stripe once in the Notis portal.
- 2Create an automation named Incident Customer Impact Review.
- 3Tell Notis to retrieve the Stripe customer identified in the webhook and summarize relevant returned details, reporting if the ID is missing.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real incident containing a Stripe customer ID.
Questions about this workflow
Does this workflow notify the customer?
No. It retrieves a Stripe customer record for internal incident review.
What if one incident affects several customers?
Supply a clear list of Stripe customer IDs in the webhook, and instruct Notis to report separately for each one. Do not infer IDs from unrelated fields.
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.