DOCUMENT OPS
Validate uploaded spreadsheet rows and route fixes back to the owner
Watches a Google Drive folder for new spreadsheets, checks every row against your schema rules.
How it runs
The automated pipeline, trigger to output.
- TriggerNew spreadsheet added to Drive intake folderGoogle Drive
- ActionDownload and parse rowsGoogle Drive
- LogicValidate each row against schema rules
- LogicBranch: clean vs. has errors
- ActionDM owner the failing rows and reasonsSlack
- OutputMove flagged file to needs-fixes folderGoogle Drive
What it does
Whenever a new spreadsheet lands in a shared Drive folder, this workflow reads every row and validates it against a schema you define (required columns, type checks, value ranges, enum membership). If any row fails, the uploader gets a Slack DM listing the precise row numbers and reasons, and the file is moved to a `needs-fixes` subfolder so it never reaches downstream systems dirty.
When to use it
Use it when teammates drop CSVs or sheets into a Drive intake folder and you keep getting malformed data — missing IDs, bad dates, wrong currency formats — that breaks the next step. It puts the fix back on the person who owns the file instead of on you.
How it works
- 1A new file in the watched Drive folder triggers the run.
- 2The file is downloaded and parsed row by row.
- 3Each row is checked against the rule set; failures are collected with row index and reason.
- 4A branch decides: clean file proceeds, file with errors is routed to remediation.
- 5The owner gets a Slack DM with the failing rows and instructions.
- 6The file is moved to the `needs-fixes` folder to quarantine it.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.