Keep customer payment follow-up visible
Use one recurring report to review customer context from incidents alongside Stripe customer records.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
Customer follow-up gets harder when incident context is scattered and billing records must be searched separately.
- Bring customer impact context and Stripe customer records into one report.
- Provide a recurring prompt to review unresolved customer follow-up.
- Report when incident data cannot be reliably connected to a Stripe customer.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and Stripe once in the Notis portal.
- 2Create an automation named Customer Payment Follow-Up Review.
- 3Tell Notis to summarize available Bugsnag customer-impact context and list relevant Stripe customers only when reliable identifiers are available, noting missing data or uncertain matches.
- 4Pick a Notis cron trigger and choose where run reports should go.
- 5Test with one run and confirm it labels unlinked records clearly.
Questions about this workflow
Will this email or message affected customers?
No. It prepares internal review context and does not send customer communications.
What if the error data has no Stripe customer ID?
The report should say the customer link is unavailable and avoid guessing based on names or unrelated details.
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.