PERSONAL PRODUCTIVITY
At-risk OKR detector with narrated Loom alert to the owner
Watches a Coda OKR doc for any key result that slips below its pace threshold, then generates a short narrated Loom explaining the gap and emails it directly to the responsible…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead key results and timelines from CodaCoda
- LogicFlag KRs projected to miss target; else stop
- ActionDraft owner-specific gap scriptOpenAI
- ActionNarrate script with ElevenLabsElevenLabs
- ActionAssemble narrated Loom alertLoom
- OutputEmail Loom to KR owner via OutlookOutlook
What it does
Monitors your Coda OKR tracker and fires only when a key result falls behind the pace it needs to hit target by quarter-end. Instead of a generic Slack ping, the owner receives a personal narrated Loom that names the metric, shows the current trajectory, and states exactly how far behind it is.
When to use it
Use this when you want exception-based accountability rather than a blanket weekly report. Good for teams where OKR owners ignore dashboards but will watch a 60-second video addressed to them.
How it works
- 1The workflow runs daily and reads each key result's current value, target, and quarter timeline from Coda.
- 2A logic step computes required pace and flags any KR projected to miss target; if none are at risk, the run ends.
- 3For each at-risk KR, an LLM drafts a direct, owner-specific script explaining the shortfall.
- 4ElevenLabs narrates the script.
- 5A Loom video brief is assembled with the narration and the metric trend.
- 6Outlook sends the Loom link to that KR's owner with a clear subject line.
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 OutlookMail, calendar, contacts.
- 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.