Keep campaign refund follow-up visible
Have Notis check recent Stripe refunds on a schedule and report details your team can use for follow-up.
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 activity can be easy to miss while a campaign is active and support conversations are moving quickly.
- Keep recent refunds visible in a chosen report channel.
- Make it easier to investigate campaign support questions using available refund data.
Setup
Build it in a few focused steps.
- 1Connect Benchmark Email and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for campaign refund monitoring.
- 3In one instruction, tell Notis to review recent Stripe refunds, report available identifiers and details, and note that campaign attribution must be supplied if it is not available in connected data.
- 4Choose the recurring schedule trigger and select where run reports should go.
- 5Test with one real run and review the refund report.
Questions about this workflow
Can Stripe refunds be attributed to a particular email campaign automatically?
Only if the connected data includes a reliable campaign identifier or your instruction supplies one. Otherwise the report can show recent refunds but cannot establish campaign attribution.
Does this issue refunds?
No. It lists refund records for review and does not change payment data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Benchmark email to Stripe. A trigger fires from one place; an action lands in another.
Benchmark email 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.
Benchmark email 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.