Bring customer context into billing test investigations
Review the relevant Stripe customer record alongside Bugbug billing findings.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Billing test investigations slow down when customer details have to be found separately in Stripe.
- Retrieve a known customer record for test context.
- Reduce time spent searching across tools.
- Keep customer-level details close to the QA result.
Setup
Build it in a few focused steps.
- 1Connect Bugbug and Stripe once in Notis.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, run the billing tests and retrieve the specified Stripe customer record for relevant findings.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real run and a known Stripe test customer ID.
Questions about this workflow
Does the workflow update customer information?
No. It retrieves customer details for QA context.
What customer reference should I include?
Use a Stripe customer ID, or provide another reference only if the investigation can resolve it to a customer ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugbug to Stripe. A trigger fires from one place; an action lands in another.
Bugbug 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.
Bugbug 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.