DOCUMENT OPS

Auto-file incoming Dropbox contracts into counterparty folders

Watches a Dropbox inbox folder for new contract PDFs, extracts the counterparty name, and moves each file into the matching client folder (creating it when none exists).

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew file added to Dropbox /Contracts/InboxDropboxDropbox
  • ActionExtract counterparty name and title with OpenAIOpenAI
  • LogicBranch: does a folder for this counterparty exist?
  • ActionCreate counterparty folder if missingDropboxDropbox
  • OutputMove and rename file into counterparty folderDropboxDropbox

What it does

Keeps your Dropbox contract inbox empty by routing every newly uploaded agreement into a folder named after the other party to the contract. New counterparties get a fresh folder automatically, so nothing ever piles up unsorted.

When to use it

When contracts arrive in a shared Dropbox inbox from many sources (sales, legal, partners) and someone has to manually drag each one into the right client folder. Ideal for ops or legal-ops teams that file by counterparty rather than by date.

How it works

  1. 1A new file landing in the Dropbox `/Contracts/Inbox` folder triggers the run.
  2. 2The file's text is read and sent to OpenAI to identify the counterparty/company name and contract title.
  3. 3A branch checks whether a folder for that counterparty already exists in `/Contracts/Clients`.
  4. 4If not, the workflow creates the counterparty folder in Dropbox.
  5. 5The contract is moved out of the inbox into the counterparty folder, renamed to a clean `Counterparty - Title - Date` convention.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect OpenAIModels, embeddings, files.
  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.