See the charge details beside the error report
Get the transaction facts needed for diagnosis in the same run 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 Charge Details
Retrieves full details for an existing stripe charge using its unique id.
Why this helps
Diagnosing payment bugs often means switching from the error record to Stripe and searching for the right transaction.
- Retrieve the charge by its supplied unique Stripe ID.
- Summarize available charge details alongside the reported error context.
- Surface missing or invalid charge 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 charge diagnosis.
- 3In one instruction, ask Notis to retrieve the supplied charge ID and summarize relevant transaction details with the error report.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real error report that includes a valid Stripe charge ID.
Questions about this workflow
Will this look up a charge if the webhook has no ID?
No. The Stripe action retrieves charge details using a unique charge ID, so the request must include one.
Does retrieving charge details change the payment?
No. This workflow only retrieves and summarizes existing charge information.
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.