Process clear Stripe refund requests from call transcripts
Give refund requests a clear path from spoken conversation to Stripe, with the transcript and payment reference in the run report.
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
Refund requests buried in calls can be missed, delayed, or processed without enough payment detail.
- Catch explicit refund requests without replaying calls
- Require a usable charge or payment intent reference before processing
- Send a run report that shows what Notis did or could not do
Setup
Build it in a few focused steps.
- 1Connect AssemblyAI and Stripe once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3In one instruction, ask Notis to review the transcript, create a refund only for a clear customer request with a valid Stripe charge or payment intent ID, and report missing details without guessing.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real transcript and confirm the refund outcome in Stripe.
Questions about this workflow
Does AssemblyAI provide the trigger for this workflow?
No. AssemblyAI has no trigger events in this setup. A Notis webhook starts the automation when it receives a request containing the transcript and relevant payment reference.
Will it refund an unclear request?
It should only create a refund when the transcript clearly expresses a refund request and the request includes a valid Stripe charge or payment intent ID. Otherwise, it can report what is missing.
Can I use a transcript without a payment reference?
Yes, but Notis cannot safely select a Stripe payment from the transcript alone. Include the relevant ID in the webhook request or have Notis report that it is missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AssemblyAI to Stripe. A trigger fires from one place; an action lands in another.
AssemblyAI 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.
AssemblyAI 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.