FINANCE

Stripe Failed-Payment Dunning with Smart Retry Cadence

When a Stripe subscription invoice fails, this workflow schedules a tuned retry sequence and sends staged email reminders.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe invoice.payment_failed webhookStripeStripe
  • LogicPick retry cadence by decline reason and plan tier
  • ActionReschedule next collection attempt in StripeStripeStripe
  • ActionSend staged dunning reminder emailOutlook
  • OutputLog outcome and tag exhausted accounts for churn-save

What it does

Turns a single failed Stripe invoice into a managed multi-touch recovery sequence. Instead of relying on Stripe's flat retry schedule, it spaces retries by failure reason and customer tier, then sends matching reminder emails so the customer can self-cure before the subscription cancels.

When to use it

Run this when involuntary churn (expired cards, insufficient funds) is eating MRR and Stripe's default Smart Retries aren't recovering enough. Best for SaaS teams with tiered plans where high-value accounts deserve a gentler, longer cadence.

How it works

  1. 1A Stripe `invoice.payment_failed` webhook fires the workflow with the invoice, customer, and decline code.
  2. 2Logic branches on decline reason and plan tier to pick a retry cadence (e.g. 3 attempts over 7 days for SMB, 5 over 14 for enterprise).
  3. 3The workflow asks Stripe to update the invoice's next collection attempt to the computed date.
  4. 4A staged reminder email goes out via Outlook, with copy escalating from soft nudge to final notice based on attempt number.
  5. 5Outcome is logged: on recovery it stops the sequence, on exhaustion it tags the customer for the churn-save team.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.