DOCUMENT OPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerNew signed file in Google Drive deal folderGoogle Drive
- ActionClassify file to deal and checklist itemOpenAI
- ActionMark checklist item received in NotionNotion
- LogicAll required documents present?
- OutputSet Notion deal-room status to ready or keep openNotion
What it does
Monitors a Google Drive folder where countersigned documents are deposited per deal. For every new file it identifies which deal it belongs to and which checklist item it satisfies (master agreement, each exhibit, W-9, board consent), updates that deal's required-documents checklist in Notion, and computes whether the packet is now complete. When the last required item arrives, it flips the deal room status to ready.
When to use it
Use it when each deal has a defined set of required documents and you track completeness in Notion, but matching incoming files to checklist items by hand is slow and error-prone.
How it works
- 1A new file in the Google Drive signed-docs folder triggers the run.
- 2The file is read and classified to a deal and a specific checklist item via OpenAI.
- 3The matching item on the deal's Notion checklist is marked received with the file link.
- 4A branch evaluates whether all required items are now checked off.
- 5If complete, the Notion deal-room page status is set to ready; if not, it stays open with remaining items listed.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect NotionPages, databases, comments.
- 3Connect OpenAIModels, embeddings, files.
- 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…
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.