DOCUMENT OPS

Triage counterparty redlines arriving by email against the template

Catches inbound emails carrying a redlined contract draft, extracts the proposed changes, compares them to the approved template.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerInbound email with redlined contract arrivesGmailGmail
  • ActionExtract redline and load approved template from DriveGoogle DriveGoogle Drive
  • ActionTier each proposed change by acceptabilityOpenAI
  • LogicSplit routine edits from policy violations
  • OutputDraft risk-tiered reply with legal escalation noteGmailGmail

What it does

When a counterparty emails back a marked-up draft, this workflow reads the attachment, isolates their proposed clause changes, and weighs each against the approved template. It returns a risk-tiered breakdown — accept, negotiate, or reject — and prepares an escalation for anything outside policy, so deal owners get an instant read before responding.

When to use it

Use it in active negotiations where redlines flow in by email and a non-lawyer deal owner needs to know quickly which edits are routine and which require legal sign-off, without waiting in the review queue.

How it works

  1. 1An incoming email with a contract attachment triggers the run.
  2. 2The redlined draft is extracted and the approved template is pulled from Drive.
  3. 3An OpenAI model maps each proposed change to a clause and tiers it by acceptability.
  4. 4A logic step splits routine edits from policy-violating ones.
  5. 5A summary reply is drafted back to the deal owner via Gmail, and a legal escalation note is appended for any rejected clauses.

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.