DOCUMENT OPS
AI-assisted spreadsheet repair that proposes corrections for malformed rows
On upload, an agent validates each row and for fixable errors proposes a normalized correction (dates, casing, formats).
How it runs
The automated pipeline, trigger to output.
- TriggerNew spreadsheet uploaded to DriveGoogle Drive
- ActionAgent parses and validates each rowOpenAI
- LogicPropose corrections; separate fixable from unfixable
- ActionSend owner original-vs-proposed diff for approvalSlack
- OutputWrite approved cleaned file back to DriveGoogle Drive
What it does
Beyond catching bad rows, this agent-driven workflow tries to repair them. For each failing row it reasons about the likely intended value — reformatting dates, normalizing state codes, trimming and casing names, coercing currency — and produces a suggested correction. The owner receives a Slack message showing original versus proposed values and approves or rejects; on approval the corrected file is saved back to Drive.
When to use it
Use it when most upload errors are formatting noise rather than missing data, and you'd rather have a human approve auto-fixes than manually retype rows. It pairs an agent's judgment with a required human checkpoint.
How it works
- 1A new spreadsheet in Drive triggers the run.
- 2The agent parses and validates each row.
- 3For fixable rows the agent proposes a normalized correction; unfixable rows are flagged separately.
- 4The owner gets a Slack diff of original vs. proposed and approves.
- 5On approval, the corrected rows are merged and the cleaned file is written back to Drive.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.