FINANCE
Stripe Dispute Delivery Proof Collector
On a new dispute, locates the shipping or digital-access proof for the order and uploads timestamped delivery evidence to a Dropbox folder named for the dispute.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe dispute created webhookStripe
- ActionLook up fulfillment and tracking in PostgresPostgres
- LogicBranch on physical vs digital delivery
- ActionFormat delivery proof document
- OutputUpload proof to dispute Dropbox folderDropbox
What it does
This workflow focuses on the single hardest evidence type to find under deadline: proof that the customer received what they paid for. When a dispute opens, it looks up the fulfillment record, retrieves the carrier tracking event or digital-access log, and saves timestamped delivery proof into a dispute-specific Dropbox folder.
When to use it
Use this when 'item not received' is your most common dispute reason and your delivery proof lives in a database or fulfillment table rather than in Stripe. It standardizes how proof of delivery is captured so it is always submission-ready.
How it works
- 1A Stripe `charge.dispute.created` webhook fires with the charge ID.
- 2The flow looks up the matching fulfillment and tracking record in Postgres.
- 3A logic step branches on fulfillment type: physical shipment versus digital access.
- 4It formats the carrier delivery confirmation or the access/login timestamps into a proof document.
- 5The proof is uploaded to a dispute-named Dropbox folder ready to attach to the Stripe response.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DropboxFiles and folders.
- 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
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.