PERSONAL PRODUCTIVITY
Loom Standups into a Coda Tracker with Blocker Escalation
Transcribes each daily Loom update into a structured Coda standup table and flags any stated blockers to the channel so they get unblocked the same day.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run after update window
- ActionCollect Loom updates and fetch transcriptsLoom
- ActionParse transcript into done/next/blockers fieldsOpenAI
- ActionAppend dated standup row per person to CodaCoda
- LogicDetect whether a blocker was stated
- OutputEscalate blockers with owners to SlackSlack
What it does
This workflow turns spoken Loom standups into structured rows in a Coda doc. The agent parses each transcript into separate fields for yesterday's work, today's plan, and blockers, then appends a dated row per person. When someone explicitly says they're blocked, it escalates that item to a Slack channel so a teammate can clear it before the day is lost.
When to use it
Use it when leadership wants a queryable history of standups, not an ephemeral chat thread, and when blockers tend to sit unnoticed for days. Good for teams that report progress in Coda dashboards.
How it works
- 1A scheduled trigger runs after the daily update window closes.
- 2The flow collects the day's Loom updates and fetches each transcript.
- 3The agent extracts structured fields: done, next, blockers, and confidence.
- 4Each parsed update is written as a new dated row in the Coda standup table.
- 5A logic step checks whether any blocker text is present.
- 6If blockers exist, the flow posts them with owner mentions to Slack for same-day resolution.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect CodaDocs, packs, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 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 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.