DOCUMENT OPS
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
How it runs
The automated pipeline, trigger to output.
- TriggerContract attachment arrives by emailGmail
- ActionParse attachment and extract clausesOpenAI
- ActionDiff clauses vs templates and assign risk tierOpenAI
- LogicBranch high-risk vs low-risk deviations
- OutputEscalate high-risk to Slack, auto-clear low-riskSlack
What it does
Catches inbound emails carrying contract attachments, diffs the document's clauses against your approved templates, and makes a routing decision: contracts with only low-risk or cosmetic edits get auto-acknowledged, while any high-risk deviation (indemnity, liability cap, termination, payment terms) is escalated to legal with the specific language flagged. It turns the shared contracts inbox into a self-sorting queue.
When to use it
Use it when counterparties send marked-up contracts by email and your team wastes time opening every attachment just to learn most are routine. Best for high-volume sales or procurement pipelines where only a fraction of redlines actually need a lawyer.
How it works
- 1A new email with a document attachment in the monitored inbox triggers the run.
- 2The attachment is parsed and its clauses extracted.
- 3An OpenAI step diffs each clause against the approved template and assigns a risk tier per deviation.
- 4A logic branch separates high-risk from low-risk contracts.
- 5High-risk contracts post an escalation to the Slack legal channel with flagged clauses; low-risk ones get a logged auto-acknowledgement.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 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
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…
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.