Turn an approved Autobound resolution into a Stripe refund
Close the loop on an approved customer resolution with a Stripe refund action.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Why this helps
Approved refunds can sit in a handoff queue while the customer waits for a resolution.
- Reduce delay after an approved resolution
- Use a charge or payment intent identifier from the signal
- Keep a record of the refund run
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 create the specified Stripe refund only when an approved-resolution webhook identifies a charge or payment intent and refund amount.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real approved resolution example.
Questions about this workflow
Can this create a partial refund?
Yes. The Stripe action supports full or partial refunds. The webhook instruction should specify the intended amount when a partial refund is approved.
What happens if the payment identifier is missing?
Stripe requires a charge ID or payment intent ID. Make sure the webhook includes one before asking Notis to issue the refund.
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.