DOCUMENT OPS

Auto-file inbound Dropbox PDFs into folders by document type

Watches a Dropbox inbox folder, classifies each new PDF (invoice, contract, receipt, statement, other), then moves it into the matching type folder.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew PDF added to Dropbox /InboxDropboxDropbox
  • ActionDownload file and extract textOpenAI
  • ActionClassify document type with confidence scoreOpenAI
  • LogicBranch: confident type vs. low-confidence → unsorted
  • OutputMove file to matching Dropbox type folderDropboxDropbox

What it does

Monitors a single Dropbox "inbox" folder for newly added PDFs, reads the text of each file, classifies it into one of five document types, and moves the file into the correct destination folder. Anything it can't confidently classify lands in an `unsorted/` folder for human review, so nothing is silently misfiled.

When to use it

Use it when documents arrive in one shared Dropbox folder from scanners, email-to-Dropbox rules, or vendors, and someone is manually dragging them into the right subfolder every day. Best for teams that already keep a consistent folder taxonomy.

How it works

  1. 1A new file added to `/Inbox` triggers the run.
  2. 2The flow downloads the file and extracts its text via OpenAI.
  3. 3A classifier assigns one document type with a confidence score.
  4. 4A branch checks confidence: below threshold routes to `unsorted/`, otherwise to the matching type folder.
  5. 5The file is moved (not copied) into the destination folder in Dropbox, leaving the inbox clean for the next drop.

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.