DOCUMENT OPS
Turn emailed contract attachments into scored register entries
Watches an intake inbox for emails with contract attachments, extracts and risk-scores the clauses with AI, files the original to Dropbox, and logs a register row in Coda.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email with attachment in intake inboxGmail
- LogicKeep only contract-type attachments
- ActionArchive original file to DropboxDropbox
- ActionExtract and risk-score clausesOpenAI
- OutputWrite scored register row to CodaCoda
What it does
Makes a shared intake mailbox the front door for contracts. When a counterparty emails an agreement, it pulls the attachment, runs clause extraction and risk scoring, archives the original file to Dropbox for the record, and records a register row in Coda — all without anyone manually saving the attachment or copying details.
When to use it
Use it when contracts reach you by email rather than a shared drive, and you want every emailed agreement captured, archived, and triaged the moment it arrives. Good for a contracts@ or procurement@ inbox.
How it works
- 1A new email with an attachment in the intake mailbox triggers the run.
- 2A logic step keeps only emails whose attachment is a contract-type document (PDF or DOCX).
- 3The attachment is saved to the Dropbox contracts archive.
- 4OpenAI extracts the key clauses and scores each for risk with a rationale.
- 5A register row is written to Coda capturing the sender, file link, clauses, and risk levels, ready for review.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect DropboxFiles and folders.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect CodaDocs, packs, automations.
- 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.