DOCUMENT OPS
Intake NDAs emailed to a shared inbox and route by signature status
Watches a shared Gmail inbox for NDA attachments, classifies each as fully signed or awaiting signature, archives the signed ones to S3.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email with NDA attachment hits shared inboxGmail
- ActionExtract text and classify signature completenessOpenAI
- LogicBranch on fully signed vs. awaiting signature
- ActionArchive fully signed NDAs to S3AWS S3
- OutputFlag unsigned NDAs to legal channel in SlackSlack
What it does
Turns a shared NDA intake mailbox into a sorting machine. Every inbound email with a contract attachment gets read, classified by signature state, and routed: fully executed agreements go straight to the archive and register, while drafts missing a signature get surfaced to legal for follow-up.
When to use it
Use it when counterparties email NDAs to a generic address like legal@ or contracts@ and someone has to manually triage signed versus unsigned all day. This removes the human sorting step and stops half-signed documents from being filed as complete.
How it works
- 1A new email with a PDF attachment arrives in the watched Gmail inbox and triggers the run.
- 2The attachment text is extracted and a model determines whether all required signature blocks are filled.
- 3A branch routes on signature status.
- 4Fully signed documents are uploaded to the S3 archive and logged as complete.
- 5Unsigned or partially signed documents are posted to the legal Slack channel with the sender and a note on what's missing, closing the loop either way.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 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.