Investigate failed payment intents with a test run
Use a failed payment intent as a cue to run the Bugbug test that covers your payment path, then review the result in your report channel.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Run test
Execute a test in bugbug and return the test run details. this action allows you to run a specific test with optional configuration for browser, device, viewport, and variable overrides. it returns detailed information about the test run including step-by-step execution status.
Why this helps
Payment failures can demand investigation, but starting the relevant test by hand adds another step when attention is already split.
- Starts a named payment test after a failed payment intent event.
- Makes the resulting test run easier to find and review.
- Reduces the need to switch to Bugbug to start an investigation.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Bugbug once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel to create one.
- 3In one instruction, name the Bugbug payment test to run after a failed payment intent.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports go.
- 5Test with one real example and confirm the report is useful.
Questions about this workflow
Does the workflow retry the Stripe payment?
No. The available Bugbug action runs a test. This workflow does not retry or change the Stripe payment.
Can it tell me why the payment failed?
The trigger is a failed payment intent, and the action runs your named Bugbug test. Use Stripe's own event details to investigate the payment reason.
Can the test vary based on the failure reason?
Only if the relevant behavior is supported by the test and information available to Notis. Specify the test outcome you want in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Bugbug. A trigger fires from one place; an action lands in another.
Stripe triggers
Bugbug actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get test run details
Get detailed information about test runs from bugbug. this action retrieves test run details with optional filtering parameters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List suites
List all available test suites in the bugbug platform. this tool makes a get request to the /suites/ endpoint and returns a list of available test suites with pagination support.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
List tests
Retrieves a list of all available tests in the bugbug account. this action provides access to all tests in the account with pagination support. it returns basic information about each test including its id, name, description, and timestamps.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Run test
Execute a test in bugbug and return the test run details. this action allows you to run a specific test with optional configuration for browser, device, viewport, and variable overrides. it returns detailed information about the test run including step-by-step execution status.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Bugbug, 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 Bugbug.