Turn failed Stripe payments into a clear follow-up contact
Keep failed payments from disappearing into a dashboard. Add the customer to Dialmycalls so someone can reach out.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Add Contact
Tool to add a contact to your contact list. use when you need to store a new contact's phone (and optional name, email, or group) before sending messages.
Why this helps
Failed payments are easy to miss, especially when follow-up means checking Stripe and entering a number somewhere else.
- Capture a reachable customer as soon as a payment fails.
- Reduce manual copying between Stripe and Dialmycalls.
- Give the team a contact to follow up with.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Dialmycalls once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction that Notis should add the failed payer as a Dialmycalls contact using available customer details.
- 4Pick the Stripe Payment Intent Failed trigger and choose where run reports should go.
- 5Test with one real failed payment and confirm the contact was added.
Questions about this workflow
Which Stripe event starts this automation?
It starts when a payment intent fails in Stripe.
What contact details can be added?
Notis can use details available in the Stripe event, such as the customer's phone and name. If the event lacks a phone number, supply it through your process or add it manually.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Dialmycalls. A trigger fires from one place; an action lands in another.
Stripe triggers
Dialmycalls actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Access Account
Tool to add a new access (sub) account. use when you need to delegate dialing capabilities to another user after setting up your master account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Contact
Tool to add a contact to your contact list. use when you need to store a new contact's phone (and optional name, email, or group) before sending messages.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Add Group
Tool to add a new contact group. use after deciding the group name to organize recipients into groups.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Delete Access Account
Tool to delete an access (sub) account by id. use when removing a sub account after deprovisioning.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete Caller ID
Tool to delete a caller id. use when you need to permanently remove an existing caller id no longer in use.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Contact
Tool to delete a contact by id. use when you need to permanently remove a contact from your list.
Product Created Trigger
Triggered when a product is created in Stripe
Delete Group
Tool to delete a contact group by id. use when you need to remove an existing contact group after confirming its id.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Delete Recording
Tool to delete a recording by id. use when you need to permanently remove a custom recording after confirming its recording id.
Connect any two apps with Notis in the middle.
Stripe and Dialmycalls, 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 Dialmycalls.