Find subscriptions relevant to a billing error
Narrow the subscription context around an incident so the next billing decision is easier to make.
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
A billing error can leave several possible subscriptions to check, making investigation slow and easy to abandon.
- Filter subscriptions using supported customer, price, status, collection method, or date context.
- Summarize relevant returned subscriptions for triage.
- Use valid subscription cursors for pagination.
Setup
Build it in a few focused steps.
- 1Connect Bug Recorder and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for subscription triage.
- 3In one instruction, ask Notis to list subscriptions with the supplied supported filters and summarize relevant results, noting when the scope is too broad.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real billing error and a supported subscription filter.
Questions about this workflow
Will the workflow cancel or update a subscription?
No. It lists subscriptions for review; changing a subscription requires a separate action.
What if no filter is supplied?
Ask Notis to report that a useful filter is missing rather than draw conclusions from an overly broad result set.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bug Recorder to Stripe. A trigger fires from one place; an action lands in another.
Bug Recorder 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.
Bug Recorder 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.