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.

CategoryProject Management
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

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 recordAirtableAirtable
  • 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

  1. 1A webhook fires when a blocking link is added to a task record in your Airtable project base.
  2. 2A filter checks whether the blocked task belongs to a milestone's critical path; non-critical edits are dropped.
  3. 3The flow reads the dependency table to trace every task downstream of the newly blocked one.
  4. 4It tags each downstream task with its squad and projected delay window.
  5. 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.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.