FINANCE
Dispute Missing-Docs Triage and Owner Assignment
Checks each new Stripe dispute against the documents found in Dropbox and, when proof is incomplete, opens a Front conversation assigning the right teammate to gather what's…
How it runs
The automated pipeline, trigger to output.
- TriggerStripe dispute created webhookStripe
- ActionList order folder contents in DropboxDropbox
- LogicBranch on document completeness
- ActionOpen assigned Front conversation for gapsFront
- OutputTag dispute needs-docs in Stripe metadataStripe
What it does
Catches disputes you can't win on autopilot. It compares the dispute's reason code to the evidence available in the order's Dropbox folder, and when a required document is absent it routes a clear task to a human instead of submitting a weak packet.
When to use it
Use it when some disputes have complete paperwork and others don't, and you want machines to handle the easy ones while escalating gaps to the right person. Ideal for teams that lose chargebacks to missing signatures or absent delivery confirmations.
How it works
- 1A Stripe `charge.dispute.created` webhook starts the flow.
- 2The order folder in Dropbox is listed and matched against a checklist for that dispute reason.
- 3A logic branch evaluates completeness: full packets continue, incomplete ones split off.
- 4For incomplete disputes, a Front conversation is created in the disputes inbox, assigned to the fulfillment or support owner, with the exact missing items and the Stripe deadline.
- 5The dispute is tagged in Stripe metadata as `needs-docs` so reporting and follow-up automations can find it.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect DropboxFiles and folders.
- 3Connect FrontShared inbox, conversations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.