DOCUMENT OPS

Contract Redline Digest: Flag Indemnity & Liability Changes on New Drive Version

When a contract gets a new version in a Google Drive folder, it diffs against the prior version and posts a Slack digest highlighting any changed indemnity, liability…

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew contract version added to Drive folderGoogle DriveGoogle Drive
  • ActionRead new version and fetch prior version textGoogle DriveGoogle Drive
  • ActionDiff versions and extract changed indemnity/liability clausesOpenAI
  • LogicBranch only if a risk-bearing clause changed
  • OutputPost before/after redline digest to legal Slack channelSlack

What it does

Watches a Google Drive contracts folder for new or updated documents, compares each new version against the most recent prior version of the same contract, and produces a redline-style digest that calls out exactly which indemnity, liability cap, and limitation-of-liability clauses changed. The digest lands in Slack so legal and deal teams see risk-relevant edits within minutes instead of re-reading the whole agreement.

When to use it

Use it when counterparties send marked-up contract drafts and your team needs to know fast whether the changes touch risk-bearing clauses. Ideal for in-house legal, deal desk, or procurement teams running many parallel negotiations who can't manually diff every turn.

How it works

  1. 1A new version of a file lands in the watched Drive folder and fires the trigger.
  2. 2The workflow reads the new version's text and pulls the prior version of the same contract from Drive.
  3. 3An OpenAI step diffs the two texts and extracts clause-level changes, tagging anything under indemnity, liability, or warranty.
  4. 4A logic step checks whether any risk clause actually changed; clean redlines are skipped.
  5. 5If risk clauses moved, a formatted before/after digest is posted to the legal Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.