DOCUMENT OPS
Route low-confidence contract classifications to a Slack human-review gate before filing
Classifies each incoming Dropbox contract and, when the model's confidence is below threshold, posts it to a Slack review channel for a human to pick the correct type before it…
How it runs
The automated pipeline, trigger to output.
- TriggerNew contract in Dropbox intake folderDropbox
- ActionExtract text and classify with confidence scoreOpenAI
- LogicBranch on classification confidence threshold
- ActionPost low-confidence cases to Slack review channelSlack
- OutputCreate Notion row using confirmed typeNotion
What it does
Adds a human-in-the-loop checkpoint to contract filing. High-confidence classifications file themselves into Notion; ambiguous ones pause and ask a reviewer in Slack to confirm the contract type before anything is written.
When to use it
Use this when misfiling a contract is costly and your folder receives oddball or hybrid documents that an LLM alone gets wrong. It keeps automation fast for the easy 80% while protecting the tricky 20%.
How it works
- 1A new contract in the Dropbox intake folder triggers the run.
- 2The PDF text is extracted and sent to OpenAI, which returns a contract type plus a confidence score.
- 3A logic branch checks confidence against your threshold.
- 4If confident, the row is created in the correct Notion register immediately.
- 5If not, a Slack message with the suggested type and document summary is posted to a review channel with type-choice buttons.
- 6The reviewer's selection determines the Notion register, and the row is created with the human-confirmed type recorded.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect NotionPages, databases, comments.
- 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.