PROJECT MANAGEMENT
Pre-standup dependency-risk briefing triggered by the calendar invite
Fifteen minutes before a recurring standup, an agent reviews cross-board dependencies in Linear and ClickUp and posts a short risk briefing to the team channel so the meeting…
How it runs
The automated pipeline, trigger to output.
- TriggerCalendar fires before recurring standupGoogle Calendar
- ActionCollect blocked items and dependencies from LinearLinear
- ActionCollect blocked items and dependencies from ClickUpClickUp
- LogicAgent ranks downstream work by deadline risk
- OutputPost the risk pre-brief to SlackSlack
What it does
Ahead of a recurring standup, this workflow pulls open dependencies across both Linear and ClickUp, has an agent reason about which downstream items are most at risk from current blockers, and posts a concise briefing to the team's Slack channel so the standup opens on the real bottlenecks instead of a round-robin of updates.
When to use it
Use it when standups burn time discovering blockers live. The pre-brief surfaces the cross-board risk picture before anyone joins, so the meeting goes straight to decisions.
How it works
- 1A Google Calendar trigger fires shortly before the recurring standup event begins.
- 2The flow collects blocked items and their dependency links from Linear and ClickUp.
- 3An agent ranks the downstream work by how close it sits to a deadline behind an unresolved blocker.
- 4It drafts a short briefing naming the top at-risk threads and who owns the blocker.
- 5The briefing is posted to the standup's Slack channel a few minutes before start.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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 Project Management workflows
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.
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.
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…
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.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
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.
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.