PERSONAL PRODUCTIVITY
Coda OKR edit to narrated change-log clip on update
When an OKR row changes in Coda, captures the before-and-after, narrates a short spoken change note with ElevenLabs.
How it runs
The automated pipeline, trigger to output.
- TriggerCoda OKR row updatedCoda
- LogicDiff old vs new; skip cosmetic edits
- ActionDraft spoken change noteOpenAI
- ActionNarrate note with ElevenLabsElevenLabs
- ActionAssemble Loom change-log clipLoom
- OutputArchive audio and Loom to Google DriveGoogle Drive
What it does
Creates an audit trail of OKR changes as listenable clips. Whenever a key result's value, target, or status is edited in Coda, this workflow records what changed and produces a short narrated note plus a Loom clip, archiving both to a shared Google Drive folder for the quarter.
When to use it
Use this when OKR numbers get adjusted mid-quarter and you want a transparent, reviewable history of who changed what and why — without forcing anyone to read a raw revision log. Useful for finance and ops teams that need defensible records.
How it works
- 1A Coda row-update event triggers the workflow with the changed key result.
- 2A logic step diffs old vs. new values and skips cosmetic edits like formatting.
- 3An LLM drafts a concise spoken change note describing the delta and its owner.
- 4ElevenLabs narrates the note.
- 5A short Loom clip is assembled from the narration and the row context.
- 6The audio file and Loom link are saved to the quarter's Google Drive change-log folder.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect ElevenLabsText-to-speech, voice cloning.
- 3Connect LoomVideo transcripts, libraries.
- 4Connect Google DriveDocs, sheets, slides, files.
- 5Connect OpenAIModels, embeddings, files.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Weekly Low-Attendance Recurring Meeting Auditor
Every Friday, scans the next week of recurring calendar events, flags those where confirmed attendance keeps dropping below a threshold.
Auto-decline focus-block invites unless the organizer is a VIP
Declines meetings that overlap your focus blocks by default, but routes invites from people on your VIP allowlist to a Slack approval prompt so important asks never get…
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Weekly Subscription Audit: Find Noisy Lists Worth Unsubscribing
Once a week, analyzes which mailing lists flooded your inbox and how rarely you opened them.
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.