Check the subscription connected to an error
See the subscription context that may explain a billing issue in the same report as the application error.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve subscription
Retrieves detailed information for an existing stripe subscription using its unique id.
Why this helps
Subscription investigations lose time when the incident and customer billing record live in separate workflows.
- Retrieve a subscription using its supplied unique ID.
- Summarize returned subscription details alongside the incident.
- Surface missing or invalid subscription references for follow-up.
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 diagnosis.
- 3In one instruction, ask Notis to retrieve the supplied subscription ID and summarize details relevant to the reported error.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real incident that includes a valid Stripe subscription ID.
Questions about this workflow
Will this change the subscription?
No. It retrieves the subscription details without updating or canceling it.
What information must Bug Recorder send?
Include the unique Stripe subscription ID in the webhook payload; Bug Recorder has no listed trigger events that supply it automatically.
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.