Automate Stripe Failed-Payment Recovery with n8n and Slack

Stripe emits invoice.payment_failed when an invoice payment attempt fails. The workflow below turns that event into a concise Slack alert with an invoice reference and, when available, a customer-facing invoice link. Your team can then follow the recovery policy configured in Stripe.Stripe: Webhooks with subscriptionsStripe API: Invoice object

Stripe Trigger (invoice.payment_failed)
  → Edit Fields (keep the useful invoice details)
  → If (hosted invoice URL is present?)
  → Slack: Send message

Use only the fields your team needs. Avoid sending card details, secrets, or unnecessary customer data to a shared channel. Keep separate Stripe test and live credentials, and do not paste credential values into node expressions or Slack text.

1. 01

   Add the Stripe Trigger

   Create a workflow and add n8n’s Stripe Trigger. Connect your Stripe test credential and select invoice.payment_failed. Use the test webhook URL while developing, then the production URL when you activate the workflow. If your setup asks you to register the endpoint in Stripe Workbench, subscribe it only to the event this workflow needs.n8n: Stripe TriggerStripe: Webhooks with subscriptionsStripe: Receive and test webhook events

2. 02

   Verify the incoming webhook

   In n8n versions that expose Stripe Trigger webhook authentication, set the Stripe Signature Secret on the Stripe credential. n8n documents signature validation in supported releases; without a signature secret, a person who knows the webhook URL could send a forged event. Use the endpoint’s actual signing secret, never an example value.n8n: Stripe TriggerStripe: Receive and test webhook events

3. 03

   Inspect one event and keep the useful fields

   Run a test event and inspect the Stripe Trigger output before writing expressions. Add an Edit Fields node and map the event ID, invoice ID, customer reference if present, amount_due with currency, and hosted_invoice_url. Stripe’s Invoice object marks hosted_invoice_url as nullable; it is null before an invoice is finalized. Keep the event ID in the alert so operators can distinguish repeat deliveries.Stripe API: Invoice objectStripe: Receive and test webhook events

4. 04

   Branch when the invoice link is missing

   Add an If node that checks whether hosted_invoice_url is present. On the true output, prepare an alert with that link. On the false output, send the invoice ID and ask the operator to open it in Stripe. Do not render an empty URL as a customer action.Stripe API: Invoice object

5. 05

   Send a readable Slack triage message

   Add the Slack node and choose Message → Send. Select the billing channel and map the tested fields into a compact message: “Stripe invoice payment failed · invoice [invoice ID] · [amount] [currency] · customer [reference]”. Include the hosted invoice link only on the branch where it exists. Tell the operator to check the invoice in Stripe before contacting the customer.n8n: Slack nodeStripe API: Invoice object

6. 06

   Set the recovery policy in Stripe

   Decide retries and customer notices in Stripe Billing, not by repeatedly issuing payment attempts from n8n. Stripe documents Smart Retries and customer notification as possible responses to invoice.payment_failed. When an invoice requires customer authentication, also listen for invoice.payment_action_required and route it as a distinct “customer action needed” case.Stripe: Webhooks with subscriptions

7. 07

   Add a failure path for the automation itself

   For a workflow that needs operational monitoring, create a second workflow whose first node is Error Trigger, then attach it as the main workflow’s error workflow in Settings. Send a separate alert with the failed workflow name and execution link. n8n notes that an error workflow does not run when the main workflow is tested manually, so verify it with an automatic test execution.n8n: Error Trigger node

1. 01

   Listen on the test webhook

   In the n8n editor, put the Stripe Trigger into test/listen mode and use its test URL. For a local test, Stripe CLI can forward events to that URL; copy the webhook signing secret printed by the CLI into the n8n Stripe credential used for this test.Stripe: Receive and test webhook eventsn8n: Stripe Trigger

2. 02

   Send a failed-invoice test event

   With the Stripe CLI authenticated to a test account and forwarding to the n8n test URL, trigger invoice.payment_failed. Stripe lists this event as supported by the CLI. The CLI creates test API objects as part of a trigger, so keep it pointed at test mode.Stripe CLI: Trigger test webhook eventsStripe: Webhooks with subscriptions

3. 03

   Check both sides of the workflow

   Confirm the event appears in n8n, the field mappings match the received invoice, the correct If branch runs, and exactly the intended Slack channel receives a message. Verify that a missing hosted invoice URL creates a useful invoice-ID alert instead of a broken link. No production payment or delivery result is implied by this test.

4. 04

   Activate only after review

   After checking the event, message, channel access, signature verification, and Stripe retry policy, switch to the production webhook and credentials. Confirm that the production endpoint is publicly reachable over HTTPS before relying on it.Stripe: Receive and test webhook eventsn8n: Stripe Trigger

stripe listen --forward-to <n8n-test-webhook-url>
stripe trigger invoice.payment_failed

Buyers import and run the workflow in their own n8n account, using their own Stripe and Slack credentials. NodePact sells the blueprint; it does not execute or host third-party automations.