Review refund trends with public issue research
See refund activity alongside the public signals relevant to your product, all in one recurring review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Refunds
Lists stripe refunds, sorted by creation date descending (newest first), with optional filtering by charge or payment intent and pagination support.
Why this helps
Refund trends and public reports about product issues can be reviewed separately, leaving patterns harder to notice.
- Bring refund data and relevant public signals into one review.
- Spot clusters that may deserve investigation.
- Separate observed patterns from conclusions that need more evidence.
Setup
Build it in a few focused steps.
- 1Connect Bright Data MCP and Stripe once in Notis.
- 2Create an automation in the portal or tell Notis what to do in plain language.
- 3In one instruction, specify which refunds and public issue signals to summarize, and how to label evidence versus hypotheses.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real refund example and review the report.
Questions about this workflow
Will this automatically change refunds?
No. List Refunds retrieves refunds for analysis; it does not issue or modify them.
Can it prove why a refund happened?
Refund records may include relevant data, but public information alone may not establish a cause. Ask Notis to label correlations as hypotheses.
Can I limit the review to certain charges?
Your instruction can specify a scope supported by the returned refund data, such as a charge or payment intent when available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bright Data MCP to Stripe. A trigger fires from one place; an action lands in another.
Bright Data MCP 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.
Bright Data MCP 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.