Review Stripe refund history from BrowserAct tasks
Bring refund history into the same workflow as the browser research that prompted the question.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 history is easy to overlook when payment research and customer context are spread across tools.
- Find refund records relevant to the research task.
- Summarize results for a response or investigation.
- Keep the workflow read-only until a separate action is authorized.
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Ask Notis to use the BrowserAct report to find related refunds and summarize the records for follow-up.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real refund history question.
Questions about this workflow
Can it find refunds if the report lacks a charge or payment intent?
A charge or payment intent identifier makes the search more reliable. If the report lacks enough information, Notis should report what is missing.
Does it issue another refund?
No. This workflow only lists and summarizes existing refunds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BrowserAct to Stripe. A trigger fires from one place; an action lands in another.
BrowserAct 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.
BrowserAct 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.