DOCUMENT OPS
Board-deck orphan citation finder
On demand, scans a board deck for every figure footnote and verifies each one points to a real, locatable cell in the Airtable source of record.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator runs reconciler on a deck
- ActionRead deck from DriveGoogle Drive
- ActionExtract figures and claimed source refsOpenAI
- ActionResolve refs against Airtable schemaAirtable
- LogicClassify resolved, orphan, or unsourced
- OutputSend orphan-citation summary to SlackSlack
What it does
Rather than only checking values, this verifies traceability: every cited number must reference a source that actually exists. It catches footnotes pointing at deleted or renamed cells, and numbers presented with no citation at all.
When to use it
Use this when your concern is citation hygiene and provenance, for example before an audit or diligence process where reviewers will click through every footnote and expect it to resolve.
How it works
- 1An operator runs the flow manually against a chosen deck.
- 2The deck is read from Google Drive.
- 3An OpenAI step extracts each figure together with the footnote or source reference it claims, including figures that carry no citation.
- 4Each claimed reference is resolved against the Airtable source-of-record schema to confirm the row and field exist.
- 5A logic step classifies each figure as resolved, orphan citation, or unsourced.
- 6A Slack summary lists every orphan and unsourced figure with its deck location so they can be cited or corrected.
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.