Prepare Voice Options for Payment Recovery
A failed payment can trigger a quick voice availability check while your team plans a helpful recovery touchpoint.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
List Voices
Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.
Why this helps
Payment issues need timely attention, and switching from billing review to audio preparation can create extra mental overhead.
- Make voice research part of payment recovery preparation.
- Check available voices in a language your team provides.
- Keep the workflow focused on a review step that the available action supports.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Aivoov once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3Ask Notis in one instruction to retrieve Aivoov voices for the language your team supplies for recovery communications.
- 4Pick Stripe Payment Intent Failed as the trigger and choose where run reports go.
- 5Test with one real failed payment intent and confirm the report is actionable.
Questions about this workflow
Will this retry the payment or contact the customer?
No. This workflow only retrieves available Aivoov voices. Payment retries and customer contact are not among the listed actions.
What if our recovery message has no chosen language yet?
Ask for a general voice list, or provide the language once your team decides. The payment event alone does not specify one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Aivoov. A trigger fires from one place; an action lands in another.
Stripe triggers
Aivoov actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Voices
Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Aivoov, 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 Aivoov.