Stripe Payment Failed: Alert Team + Email Customer

A payment fails in Stripe. The customer never hears from you. Two days later they cancel. This happens constantly — because Stripe logs the failure and moves on, and nobody is watching the dashboard 24/7. This Make.com tutorial shows you how to automate Stripe failed payment alerts — the automation reacts the moment a payment fails: the customer gets an email within seconds, and your team gets an alert. No developer needed, no manual checking.

Why Missed Failed Payments Cost You More Than You Think

Every failed payment that goes unaddressed is a potential churn. Customers don't always know their card failed — they assume you'll reach out. When you don't, they assume the worst and move on. Speed matters: a same-day email from you reads as professional and attentive. A silence that lasts three days reads as a company that doesn't care. The good news is this is completely fixable with a simple automation. Once it's set up, it runs forever.

Doesn't Stripe Already Send Failed Payment Emails?

Yes — but with important limitations that make it the wrong solution for most businesses. Stripe's built-in Smart Retries and dunning emails only work for subscription billing (recurring charges). If you send one-time invoices, Stripe won't automatically email your customer at all. Even for subscriptions, the emails are generic Stripe-branded messages that many customers confuse with spam or phishing. You can't add your logo, your tone, or a direct link to update payment details in your own portal. And critically — your team gets no alert. Nobody on your side knows a payment failed unless they check the Stripe dashboard manually. The automation in this guide solves all of that: it works for every invoice type, sends email from your own Gmail account, and notifies your team the same second it fires.

What This Automation Does

When a payment fails in Stripe, Make.com catches the event instantly and runs three actions automatically: it identifies the customer, sends them a personalized email with their invoice details, and your team can add a Slack alert so someone can follow up if needed.

How the Workflow Runs

The whole setup takes about 20 minutes. After that, it runs on its own.

How to Set Up the Automation

1. Create a Stripe account and add a test customer — open Stripe, go to Billing → Invoices, and create a test invoice. You'll use Stripe's sandbox mode throughout this guide, so no real payments are involved.

2. 

3. Log in to Make.com and create a new scenario — click the large + button on the canvas and search for "Stripe." Select the Watch Events module. This is the trigger that listens to your Stripe account.

4. 

5. Click "Create a webhook" — Make.com will ask you to connect your Stripe account. Use API Key authentication: copy your Secret key from Stripe → Developers → API keys (it starts with sk_test_ for sandbox). Set the Group to "Invoice" and check "Invoice payment failed" as the event to watch.

6. 

7. Add a filter between your Stripe trigger and the next module — click the line between modules and select "Add a filter." Set the label to "Invoice Payment Failed," the condition to Event Type, the operator to Equal to, and the value to invoice.payment_failed. This prevents the workflow from running on unrelated Stripe events.

8. 

9. Add a Stripe "Retrieve a Customer" module — click the + button and search for Stripe again. Select "Retrieve a Customer." This step is essential: when Stripe sends a payment failed event, it includes the customer's ID but not their name or email. This module fetches the full customer profile.

10. 

11. Map the Customer ID field to the customer object from your Stripe trigger — in the Retrieve a Customer configuration, set Customer ID to "2. Object: Customer" from the previous module. This tells Make.com which customer to look up.

12. 

13. Add a Gmail "Send an email" module — click + and add Gmail. Connect your Google account when prompted. Map the To field to "7. Email" from the Retrieve a Customer module. For the Subject, type "Payment Failed: Invoice" and then map "2. Object: Number" so each email shows the real invoice number.

14. 

15. Map the email body with dynamic fields — in the Body field, write your message and map three fields from Stripe: the customer's name (7. Name), the invoice amount (2. Object: Amount due), and the invoice number (2. Object: Number). The result is a personalized email that looks like it was written by hand.

16. 

17. 

18. Save the scenario — your canvas should now show three modules connected: Stripe Watch Events → Stripe Retrieve a Customer → Gmail Send an email.

19. 

20. Test the workflow — use the Stripe CLI to send a test event without touching any real data. Run stripe trigger invoice.payment_failed in your terminal. Make.com will process it and send the email to your test customer automatically. If you don't have the Stripe CLI, install it with brew install stripe/stripe-cli/stripe on Mac, then run stripe login first.

21. 

22. 💡 Pro Tip: After the Gmail module, add a Slack "Create a Message" module to alert your billing channel the moment a payment fails. Something like: "Payment failed — [Customer Name], Invoice [Number], Amount: [Amount Due]. Follow up today." Now both the customer and your team know immediately — and someone can pick up the phone if the customer doesn't respond to the automated email.