DOCUMENT OPS

Inbound Signed-Contract Email Verifier and Filer

Watches the contracts inbox for emailed executed agreements, verifies the attached PDF has all required exhibits and signatures before accepting it.

CategoryDocument Ops
EngineSim + Paperclip
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email with contract attachmentGmailGmail
  • ActionExtract and verify exhibits, initials, signaturesOpenAI
  • LogicComplete vs. incomplete submission
  • ActionFile complete contract to Google Drive deal folderGoogle DriveGoogle Drive
  • OutputReply to sender requesting missing itemsGmailGmail

What it does

Monitors the shared contracts inbox for incoming emails carrying executed agreements. It opens the PDF attachment, verifies the full exhibit set, every initial block, and all signatures are present, then files complete contracts into the correct Google Drive deal folder. If anything is missing, it auto-replies to the sender listing the exact exhibits or signatures still needed, so the gap is resolved over the same email thread.

When to use it

Use it when counterparties and brokers send signed contracts by email and someone has to manually open each attachment, check it, and chase missing pages before filing.

How it works

  1. 1A new email with a PDF attachment in the contracts inbox triggers the run.
  2. 2The attachment is extracted and analyzed for exhibits, initials, and signatures via OpenAI.
  3. 3A branch splits complete from incomplete submissions.
  4. 4Complete contracts are uploaded to the matching Google Drive deal folder.
  5. 5Incomplete ones get an auto-reply to the sender itemizing exactly what is missing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  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.