DOCUMENT OPS
Daily audit of a Drive folder for unredacted sensitive documents
Runs each morning over a Google Drive folder, scans every document for PII and secrets, and posts a Slack digest ranking the riskiest files that still need redaction.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList and read documents in Drive folderGoogle Drive
- ActionScan each file for PII and secretsOpenAI
- LogicScore risk per file and drop clean files
- ActionLog flagged files to Airtable audit tableAirtable
- OutputPost ranked exposure digest to SlackSlack
What it does
On a daily schedule, sweeps a chosen Google Drive folder, scans every document for PII and secrets, scores each file's exposure risk, and delivers a prioritized digest so owners know exactly what to redact today.
When to use it
Use it for ongoing hygiene on a shared deliverables or archive folder where files accumulate and you want a recurring sweep rather than per-file gating. Good for compliance owners who need a standing audit trail and a daily worklist.
How it works
- 1A scheduled trigger fires each morning.
- 2The workflow lists all documents in the target Drive folder and reads their text.
- 3An OpenAI scan returns findings per file with categories and severity.
- 4A logic step aggregates findings into a per-file risk score and filters out clean files.
- 5The flagged files are recorded as rows in an Airtable audit table with category, severity, and link.
- 6A ranked Slack digest summarizes the top exposures and links the Airtable view for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.