PROJECT MANAGEMENT
Alert Teams when a new blocker lands on a milestone-critical task
When a blocking link is added to any task on the critical path in Airtable, instantly computes the downstream tasks now at risk and alerts the affected squads in Microsoft Teams.
How it runs
The automated pipeline, trigger to output.
- TriggerBlocking link added to an Airtable task (webhook)HTTP webhook
- LogicKeep only blockers on a milestone critical path
- ActionTrace downstream tasks from the newly blocked recordAirtable
- LogicTag downstream tasks with squad and projected delay
- OutputAlert affected squads in Microsoft TeamsMicrosoft Teams
What it does
Fires the instant someone adds a new blocking dependency to a task that sits on a tracked milestone's critical path. It immediately recomputes what that new blocker threatens downstream and warns the affected squads in Microsoft Teams before the delay propagates unnoticed.
When to use it
Use it when blockers get added mid-sprint and nobody realizes a single new dependency just put a milestone in danger. This catches the risk at the moment of the edit, not at the next standup.
How it works
- 1A webhook fires when a blocking link is added to a task record in your Airtable project base.
- 2A filter checks whether the blocked task belongs to a milestone's critical path; non-critical edits are dropped.
- 3The flow reads the dependency table to trace every task downstream of the newly blocked one.
- 4It tags each downstream task with its squad and projected delay window.
- 5A Microsoft Teams message goes to each affected squad channel naming the new blocker, the threatened milestone, and the at-risk downstream tasks.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.
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.
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.
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.
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.
