Check Stripe refunds against Autobound resolution context
Get a clear view of recent refunds and whether the related resolution context is available.
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
Refunds and customer resolutions can become disconnected, leaving teams unsure whether a case was handled.
- Review recent refunds in one place
- Spot missing resolution context for follow-up
- Avoid assuming a refund has a matching Autobound record
Setup
Build it in a few focused steps.
- 1Connect Autobound and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, tell Notis to list recent Stripe refunds and compare them with any available Autobound resolution context, flagging missing or unclear matches.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real refund review example.
Questions about this workflow
Can Notis confirm that a refund was approved in Autobound?
Only when the relevant resolution context is available to the run. Otherwise, the report should mark the approval status as unknown.
Does this workflow issue refunds?
No. It lists existing refunds and creates a review summary.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Autobound to Stripe. A trigger fires from one place; an action lands in another.
Autobound 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.
Autobound 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.