FINANCE
Assemble Stripe Dispute Evidence Packet from Order Records
When a Stripe dispute opens, pulls the matching order and shipment records from Postgres, gathers receipts and delivery proof.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe dispute created webhookStripe
- ActionLook up order and shipment in PostgresPostgres
- LogicBranch: has tracking and delivery proof?
- ActionCompose evidence fields from records
- OutputSubmit evidence to Stripe disputeStripe
What it does
When a cardholder disputes a charge, this workflow automatically builds and submits the evidence Stripe needs to fight it. It matches the disputed charge to your internal order, collects the receipt, shipping carrier, tracking number, and delivery confirmation, then files everything to the dispute through the Stripe API.
When to use it
Run this when you process card payments and want to stop letting winnable disputes lapse because nobody assembled the paperwork in time. It is built for ops and finance teams who keep order and fulfillment data in Postgres.
How it works
- 1A Stripe `charge.dispute.created` webhook fires the moment a dispute opens.
- 2The workflow reads the charge ID and looks up the matching order, customer, and shipment rows in Postgres.
- 3A branch checks whether a tracking number and delivery date exist; orders with no shipment record are routed to manual review instead of auto-filing.
- 4For shippable disputes, it composes the evidence fields (receipt, shipping address, tracking, delivery date, customer comms).
- 5It submits the assembled evidence to the Stripe dispute and marks the order as contested.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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.
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 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.
Overdue Accrual Escalation Emails to Owners and Managers
On a schedule it flags uncoded spend that has stayed open past the chase deadline and emails each delinquent owner via Gmail.
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.