DOCUMENT OPS
Triage emailed contracts and route obligations to owners
When a signed agreement arrives by email, an agent classifies the contract type, extracts obligations, assigns each to the right owner, and files the document plus a Coda summary.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email with contract attachmentGmail
- ActionClassify agreement type and extract obligationsOpenAI
- LogicRoute obligations to owners; escalate low-confidence cases
- ActionArchive original document to DropboxDropbox
- OutputWrite owner-assigned summary to CodaCoda
What it does
This agent handles executed contracts that arrive as email attachments. It reads the document, decides what kind of agreement it is, extracts the obligations, figures out which internal owner each belongs to based on type and department, archives the file, and records a structured summary — escalating anything ambiguous instead of guessing.
When to use it
Use it when contracts come in over email from counterparties and you want them sorted, summarized, and assigned without a person triaging every inbox item. The agent's judgment handles the messy variety of real-world agreements.
How it works
- 1A new email with a contract attachment triggers the run.
- 2The agent reads the attachment and classifies the agreement type and risk level.
- 3It extracts obligations and maps each to an owner using internal routing rules, escalating low-confidence cases.
- 4The original document is archived to Dropbox in the matching folder.
- 5A summary with owners and obligations is written to Coda and the assigned owners are notified.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect DropboxFiles and folders.
- 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.