Check the payment intent behind an application error
Bring the reported payment intent status into the incident report and keep diagnosis moving.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve payment intent
Retrieves a paymentintent by its id; `client secret` is required if a publishable api key is used.
Why this helps
Payment state can be unclear when an application error arrives without an immediate view into Stripe.
- Retrieve the payment intent by its supplied ID.
- Summarize the available Stripe status and payment details for the incident.
- Flag missing identifiers or client-secret requirements when applicable.
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 payment intent checks.
- 3In one instruction, ask Notis to retrieve the supplied payment intent and summarize the returned status in the incident report.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real error report containing a payment intent ID.
Questions about this workflow
Does the action confirm or retry the payment?
No. It retrieves the payment intent details; it does not confirm or update the payment.
What if the connected Stripe credentials require a client secret?
The action may require the client secret when using a publishable API key. Supply the required detail through an approved secure path or use credentials that support retrieval.
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.