DOCUMENT OPS

Emailed Contract Redraft vs Drive Baseline Reconciliation

Catches contract attachments arriving by email, compares each against the canonical baseline stored in Google Drive.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEmail with contract attachment receivedGmailGmail
  • ActionFind matching approved baseline in Google DriveGoogle DriveGoogle Drive
  • ActionDiff attachment vs baseline and tag materialityOpenAI
  • LogicRank material deltas; skip formatting-only redrafts
  • OutputReply in email thread with ranked change summaryGmailGmail

What it does

Monitors a shared legal inbox for inbound emails carrying contract attachments. For each attachment it locates the matching canonical baseline in a Google Drive contracts folder, performs a clause-by-clause comparison, and identifies the substantive deviations from your approved language. It then replies on the original email thread with a concise, ranked list of material changes plus the unchanged-clause count, so the negotiator has context without opening the file.

When to use it

Use it when counterparties send redrafts as email attachments rather than through a deal room, and you maintain an approved baseline per agreement type. Good for teams that want the change summary to live right where the negotiation conversation is happening.

How it works

  1. 1An inbound email with a document attachment triggers the flow.
  2. 2The flow searches the Google Drive contracts folder for the matching baseline by contract name.
  3. 3An OpenAI step diffs the attachment against the baseline and tags each delta with materiality and a fallback-position note.
  4. 4A logic step ranks material deltas and skips threads where only formatting changed.
  5. 5It replies on the original Gmail thread with the ranked material-change summary.

Set it up

What you configure once, before turning it on.

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