DOCUMENT OPS

On-demand clause diff between two contract versions

Triggered by a webhook with two document references, it extracts and aligns clauses across both versions, classifies every substantive change.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook with two version referencesHTTP webhook
  • ActionFetch both versions and extract clausesGoogle DriveGoogle Drive
  • ActionAlign and classify substantive changesOpenAI
  • LogicDrop cosmetic edits, keep material ones
  • OutputReturn structured clause diff to callerHTTP webhook

What it does

Given two versions of a contract, it aligns matching clauses across both, detects what materially changed (not just text edits), and labels each change as additive, restrictive, neutral, or deal-breaking against your playbook. It returns the diff as structured data so another app or reviewer dashboard can render it.

When to use it

Use it when you need clause-level diffing on demand from inside another tool, such as a contract portal or a deal-room button, rather than on a folder watch. It is the building block other workflows call when a reviewer asks "what changed since the last round?".

How it works

  1. 1A webhook fires with references to the prior and incoming contract versions.
  2. 2Both documents are fetched from Drive and their clauses extracted.
  3. 3The model aligns clauses across versions and classifies each substantive change against the playbook.
  4. 4A logic step drops cosmetic edits so only material changes remain.
  5. 5The structured diff is returned to the caller via the webhook response for rendering or further routing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  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.