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.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook with two version referencesHTTP webhook
- ActionFetch both versions and extract clausesGoogle 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
- 1A webhook fires with references to the prior and incoming contract versions.
- 2Both documents are fetched from Drive and their clauses extracted.
- 3The model aligns clauses across versions and classifies each substantive change against the playbook.
- 4A logic step drops cosmetic edits so only material changes remain.
- 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.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
