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.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe invoice.payment_failed webhookStripe
- LogicPick retry cadence by decline reason and plan tier
- ActionReschedule next collection attempt in StripeStripe
- 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
- 1A Stripe `invoice.payment_failed` webhook fires the workflow with the invoice, customer, and decline code.
- 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).
- 3The workflow asks Stripe to update the invoice's next collection attempt to the computed date.
- 4A staged reminder email goes out via Outlook, with copy escalating from soft nudge to final notice based on attempt number.
- 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.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect OutlookMail, calendar, contacts.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Detect Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Real-Time Uncoded Expense Nudge on New Spend Event
When a new expense lands without a GL code, a webhook fires and the workflow immediately Slack-nudges the spending owner to code it on the spot.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
