DOCUMENT OPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled scan
- ActionList and read contracts in Drive folderGoogle Drive
- ActionDiff clauses vs approved templates, extract deviationsOpenAI
- LogicSkip already-logged contracts and cosmetic edits
- OutputWrite each deviation as a Notion register rowNotion
What it does
Runs once a day across all contracts in a Drive folder, compares each contract's clauses to your approved template set, and records every material deviation as a structured row in a Notion review register. Each row carries the contract name, clause type, original vs. proposed wording, and a risk rating, giving legal a single auditable queue instead of scattered email threads.
When to use it
Use it when you need a durable, trackable record of clause deviations rather than a one-off alert. Good for teams that run a clause-review workflow with status columns (open, accepted, rejected) and want history of what counterparties asked to change.
How it works
- 1A daily schedule starts the run.
- 2The Drive folder is listed and each unprocessed contract is read.
- 3An OpenAI step aligns clauses to approved templates and extracts each deviation with a risk rating.
- 4A logic step skips contracts already logged and drops cosmetic-only changes.
- 5Each remaining deviation is created as a Notion database row with status set to "needs review."
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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
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.
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.
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.