DOCUMENT OPS
Weekly obligation digest with overdue escalation
Each week, compiles obligations due in the coming days from the Coda register, separates upcoming from overdue, emails a digest to the team.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionRead due-soon obligations from Coda registerCoda
- LogicPartition into upcoming and overdue
- ActionFormat owner-grouped digest with OpenAIOpenAI
- ActionEmail the digest to the teamGmail
- OutputPost overdue items to Slack escalation channelSlack
What it does
This workflow turns the obligation register into a weekly rhythm. It reads obligations from Coda, splits them into upcoming versus already overdue, sends a clean digest by email so everyone sees what is due, and escalates the overdue ones to Slack so they get chased the same day.
When to use it
Use it once you have an obligation register in Coda and want a predictable weekly readout plus an exception channel for items that have slipped. It keeps obligations visible without anyone querying the register by hand.
How it works
- 1A weekly schedule triggers the run.
- 2Obligations with due dates in the lookahead window are read from the Coda register.
- 3A logic step partitions them into upcoming and overdue buckets.
- 4OpenAI formats both buckets into a readable digest grouped by owner.
- 5The digest is emailed to the distribution list.
- 6If any overdue items exist, they are posted to the Slack escalation channel tagging the owners.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 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.