DOCUMENT OPS
NDA Risk-Flag Triage to Postgres Ledger
Scores each incoming NDA against your risk policy, routes high-risk agreements to a Slack escalation channel, and records every decision and flag in a Postgres audit ledger.
How it runs
The automated pipeline, trigger to output.
- TriggerNew NDA email in intake mailboxGmail
- ActionClassify clause risk with Hugging FaceHugging Face
- LogicBranch low-risk vs high-risk by tier
- ActionInsert NDA, flags, and tier into Postgres ledgerPostgres
- OutputEscalate high-risk NDAs to SlackSlack
What it does
Takes NDAs as they arrive, classifies each clause for risk (unlimited term, broad non-compete, one-sided indemnity, missing mutual-confidentiality), assigns an overall risk tier, and writes the full result to a Postgres ledger. High-risk agreements are pushed to a Slack channel so counsel sees them immediately instead of waiting in a queue.
When to use it
Use it when not every NDA needs the same scrutiny and you want low-risk standard forms to auto-clear while only genuinely risky terms reach a lawyer. The Postgres ledger gives you an auditable record of what was flagged and why.
How it works
- 1A new NDA email lands in the intake mailbox.
- 2A Hugging Face classifier scores each clause and produces a risk tier.
- 3A logic branch splits low-risk from high-risk based on the tier and flagged clauses.
- 4Every NDA, its flags, and the tier are inserted into the Postgres review ledger.
- 5High-risk agreements are posted to the legal escalation Slack channel with the offending clauses called out.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
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.
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.