List payment intents relevant to the error
Collect the payment intent context for an incident without hunting through Stripe manually.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List payment intents
Retrieves a list of stripe paymentintents, optionally filtered and paginated using paymentintent ids as cursors.
Why this helps
Payment investigations get harder when the error report does not identify one obvious payment intent.
- List payment intents using supported filters and pagination.
- Summarize relevant returned intents for investigation.
- Report when the webhook lacks enough context to run a useful search.
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 triage.
- 3In one instruction, ask Notis to list payment intents using only supported filters supplied in the incident context and summarize relevant results.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real incident containing a supported search scope.
Questions about this workflow
Does listing payment intents process a payment?
No. It retrieves matching payment intent records; confirming or updating an intent uses a different action.
Can it continue through multiple pages?
Yes, with valid payment intent IDs from prior responses used as pagination cursors.
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.