FINANCE

Archive Stripe Dispute Evidence Packets to Dropbox

On each new Stripe dispute, generates a single PDF evidence packet from the order, receipt, and shipment data and files it in a dated Dropbox folder for audit and bank submission.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe dispute created webhookStripeStripe
  • ActionQuery order, receipt, shipment from PostgresPostgreSQLPostgres
  • ActionRender evidence into a single document
  • ActionUpload packet to dated Dropbox folderDropboxDropbox
  • OutputSave Dropbox path to dispute recordPostgreSQLPostgres

What it does

This workflow produces a human-readable evidence packet for every Stripe dispute and stores it where your team can find it. It pulls the order and shipment data, assembles a single document covering the receipt, delivery proof, and customer correspondence, and saves it to Dropbox under a per-month dispute folder.

When to use it

Use it when you need a durable, shareable record of what you submitted for each chargeback, whether for finance audits, bank representment, or handing off to a payments analyst.

How it works

  1. 1A Stripe `charge.dispute.created` webhook triggers the run.
  2. 2The workflow queries Postgres for the order, line items, receipt, and shipment details tied to the disputed charge.
  3. 3It renders those records into a single formatted evidence document.
  4. 4It uploads the file to Dropbox into a folder named by year and month, keyed on the dispute ID.
  5. 5It writes the Dropbox file path back to the dispute row in Postgres so the artifact is traceable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect DropboxFiles and folders.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.