DOCUMENT OPS

Match inbound purchase orders against Airtable and route to Dropbox

Classifies inbound Outlook attachments as purchase orders, looks up the PO number in an Airtable orders table.

CategoryDocument Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Outlook email with attachmentOutlook
  • LogicIdentify purchase ordersHugging FaceHugging Face
  • ActionExtract PO numberHugging FaceHugging Face
  • ActionLook up PO in Airtable ordersAirtableAirtable
  • LogicBranch on match vs no match
  • OutputFile to confirmed or review Dropbox folderDropboxDropbox

What it does

Validates purchase orders before they are filed. It reads each inbound attachment, identifies POs, checks the PO number against your Airtable orders table, and sorts the document into a confirmed or needs-review Dropbox folder based on whether it matches a known order.

When to use it

Use it when customers email back signed or revised POs and you need to confirm each one corresponds to an order you actually issued before archiving. Catches stray or fraudulent POs early instead of after filing.

How it works

  1. 1A new Outlook email with an attachment triggers the run.
  2. 2The PDF is read and a classifier identifies whether it is a purchase order; other types exit.
  3. 3The PO number is extracted from the document text.
  4. 4Airtable is queried for a matching open order.
  5. 5A logic branch checks the result: a match routes to the confirmed path, no match routes to review.
  6. 6The PO is uploaded to either the confirmed or needs-review Dropbox folder named `PO_{number}_{status}.pdf`.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect AirtableBases, tables, views, automations.
  4. 4
    Connect DropboxFiles and folders.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.