DOCUMENT OPS
Detect unsigned or incomplete contracts at intake and quarantine them instead of filing
Inspects each contract dropped into Dropbox for missing signatures, blank fields, and missing effective dates.
How it runs
The automated pipeline, trigger to output.
- TriggerNew file in Dropbox intake folderDropbox
- ActionCheck signatures and required fields with OpenAIOpenAI
- LogicBranch complete vs incomplete contract
- OutputFile complete contract into Notion registerNotion
- ActionMove incomplete file to Dropbox quarantineDropbox
- ActionEmail submitter what is missingGmail
What it does
Acts as a quality gate at the front door. Before any contract reaches the Notion register, it checks that the document is actually executed — signatures present, key fields filled, effective date set — and stops incomplete ones from polluting the register.
When to use it
Use this when half-finished drafts and unsigned copies keep getting dropped into your intake folder and ending up logged as if they were final. It enforces "only executed contracts get filed."
How it works
- 1A new file in the Dropbox intake folder triggers the run.
- 2The PDF text is extracted and analyzed by OpenAI for signature presence, blank required fields, and a valid effective date.
- 3A logic branch splits complete contracts from incomplete ones.
- 4Complete contracts proceed to a row in the Notion register.
- 5Incomplete contracts are moved to a Dropbox quarantine folder.
- 6An email is sent to the submitter listing exactly what is missing so they can resubmit a corrected copy.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect GmailRead, draft, send, label.
- 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.