DOCUMENT OPS
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
How it runs
The automated pipeline, trigger to output.
- TriggerNew contract file added to Drive folderGoogle Drive
- ActionRead document and split into clausesGoogle Drive
- ActionDiff each clause vs approved template, classify changeOpenAI
- LogicKeep only material or unexpected deviations
- OutputPost deviation summary to Slack legal channelSlack
What it does
Monitors a shared Google Drive folder for new or modified contract documents. When one arrives, it extracts the clause text, compares each clause against your approved template baseline, and surfaces exactly where the counterparty redlined your standard language. Legal sees a single Slack message with the deviations, not a 40-page document to re-read.
When to use it
Use it when sales or vendors return signed-back contracts to a Drive folder and your legal or ops team needs to know quickly whether the document still matches approved terms. It removes the manual line-by-line review for the common case where most clauses are untouched.
How it works
- 1A new file in the watched Drive folder triggers the run.
- 2The document text is read and split into clauses.
- 3An OpenAI step aligns each incoming clause to the matching approved-template clause and classifies the change as none, cosmetic, or material.
- 4A logic step filters to only material or unexpected deviations.
- 5If any exist, a Slack message lists each deviation with the original vs. proposed text and a risk label; clean contracts post a short "matches template" confirmation.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
Deal-Room Intake Checklist from Google Drive Signed Folder
Audits each signed document dropped into a Google Drive folder against a Notion required-documents checklist for that deal, marks items received.
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.