FINANCE

On-Demand Dispute Packet Builder from a Charge ID

An operator submits a Stripe charge or dispute ID and the flow assembles a complete evidence packet from Dropbox order docs into a single shareable folder.

CategoryFinance
Enginesim
Difficultybeginner
Triggermanual
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator submits charge or dispute ID
  • ActionLook up charge and customer in StripeStripeStripe
  • ActionGather and copy docs into packet folder in DropboxDropboxDropbox
  • LogicVerify document types and flag gaps
  • OutputReturn shareable Dropbox link and checklistDropboxDropbox

What it does

Lets a billing teammate build a full evidence packet on demand without digging through Dropbox by hand. Given a charge or dispute ID, it gathers every relevant order document, organizes them into one clean folder, and hands back a link ready to attach to a Stripe submission.

When to use it

Use it for ad-hoc, high-value, or complicated disputes that fall outside the automatic pipeline, or when an agent wants to assemble a packet before deciding whether to fight a chargeback. It is the manual companion to the webhook-driven assembler.

How it works

  1. 1A manual trigger collects the Stripe charge or dispute ID from the operator.
  2. 2The flow looks up the charge in Stripe to resolve the order ID and customer details.
  3. 3It searches Dropbox for all matching order documents and copies them into a fresh `packet/<dispute>` folder.
  4. 4A logic step verifies each expected document type was found and notes any gaps.
  5. 5The flow returns the shareable Dropbox folder link plus a checklist of what is present and missing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.