DOCUMENT OPS

Emailed receipt attachment intake and archive

Captures receipt attachments arriving by email, normalizes the filename with vendor and date pulled from the document.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email arrives in receipts inboxGmailGmail
  • LogicKeep only messages with image or PDF attachments
  • ActionRead vendor and date with Hugging Face modelHugging FaceHugging Face
  • ActionRename file to vendor-date convention
  • OutputUpload to dated Dropbox archive folderDropboxDropbox

What it does

Standardizes how emailed receipts enter the system. When a receipt-bearing email arrives, it pulls each attachment, uses a Hugging Face model to read the vendor and date, renames the file to a consistent vendor-date convention, and stores it in a year-and-month Dropbox folder so downstream extraction and dedup steps have clean, organized input.

When to use it

Use it when staff forward receipts to a shared inbox instead of dropping files directly. It removes the chaotic mix of IMG_0421.jpg names and gets everything into one well-named archive automatically.

How it works

  1. 1A new email in the receipts inbox triggers the run.
  2. 2A logic step keeps only messages that carry image or PDF attachments and discards the rest.
  3. 3Each attachment is read by a Hugging Face model to extract vendor and date.
  4. 4The file is renamed to a vendor-date convention.
  5. 5The renamed file is uploaded to the matching dated Dropbox archive folder.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  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.