PROJECT MANAGEMENT
Nudge teammates who skipped their daily Loom standup
On a daily schedule, check who has not posted a Loom standup video by the cutoff time and send each missing person a private Slack reminder.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily after standup cutoff
- ActionList today's Loom standup videosLoom
- LogicDiff roster vs. recorded
- ActionDM each missing teammateSlack
- OutputPost nudge summary to team channelSlack
What it does
This keeps async standup honest. At a set time each workday it compares your roster against the Loom videos posted to the standup space, finds who hasn't recorded yet, and DMs each of them a friendly, personalized Slack nudge with the cutoff time.
When to use it
Use it when async standups are mandatory but compliance drifts, and you don't want a manager manually chasing people every morning. Best for teams that already agree on a daily recording deadline.
How it works
- 1A daily schedule fires shortly after the standup cutoff time.
- 2The workflow lists all Loom standup videos posted since the start of the workday.
- 3A logic step diffs the recorded set against the expected roster to compute who is missing.
- 4For each missing person, a private Slack direct message is sent reminding them to record.
- 5A short summary of who was nudged is posted to the team channel so the lead has visibility without naming-and-shaming in public.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.