FINANCE
Agentic Dunning Recovery Orchestrator
On each failed Stripe payment, an AI agent reasons over the customer's history and warehouse signals to choose a personalized recovery plan, drafts tailored outreach.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe invoice.payment_failed webhookStripe
- ActionPull customer history and signals from BigQueryBigQuery
- LogicAgent reasons over context to choose recovery plan
- ActionReschedule retry in Stripe and send tailored emailOutlook
- OutputEscalate low-confidence or high-value cases to SlackSlack
What it does
Replaces fixed dunning rules with an agent that decides per customer. For each failed payment it weighs the decline reason, account value, prior recovery behavior, and engagement signals from the warehouse, then composes a recovery plan: how aggressively to retry, what to say, and whether a human should step in.
When to use it
Use it when rigid cadences leave money on the table and your accounts are heterogeneous enough that one-size outreach underperforms. Best for teams comfortable letting an agent draft and execute outreach with guardrails.
How it works
- 1A Stripe `invoice.payment_failed` webhook starts the run.
- 2The agent pulls customer history and engagement signals from BigQuery to assess recovery likelihood.
- 3It reasons over the context to pick a retry timing and drafts a personalized email matching the situation.
- 4It executes the retry reschedule in Stripe and sends the drafted message via Outlook.
- 5Low-confidence or high-value cases are escalated to a human in Slack with the agent's reasoning attached.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect OutlookMail, calendar, contacts.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Month-End Uncoded Spend Chaser via Snowflake to Slack
On a month-end schedule, queries Snowflake for unaccrued or uncoded expenses, groups them by department owner.
Receipt Upload OCR Policy Check with Manager Escalation
When an employee drops a receipt into a Drive folder, it extracts the line items, checks them against expense policy.
Weekly Proration Anomaly Audit to Notion
Each week it aggregates all flagged proration discrepancies from Snowflake, scores them against anomaly thresholds, and publishes a finance-ready audit page in Notion with totals.
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.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Draft and Send Proration Over-Billing Correction Emails
For each confirmed over-billing credit, an agent drafts a clear, customer-specific apology email explaining the proration error and the credit applied.
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.