PROJECT MANAGEMENT

Escalate to PagerDuty when a slipped blocker threatens a hard deadline

Evaluates whether a slipped Linear blocker now endangers a fixed launch milestone on the critical path.

CategoryProject Management
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear due-date pushed-out webhookLinearLinear
  • ActionTrace critical path to launch milestoneLinearLinear
  • LogicCompute remaining buffer vs new slip
  • ActionOpen PagerDuty incident if buffer is negativePagerDutyPagerDuty
  • OutputPost at-risk warning to program Teams channelMicrosoft Teams

What it does

This workflow decides whether a slipped blocker actually matters: it walks the critical path to a fixed launch milestone, and only escalates when the slip has consumed all remaining schedule buffer.

When to use it

Use it for high-stakes programs with an immovable launch date where most slips are absorbable but a few are existential. It cuts noise by escalating only the slips that genuinely put the milestone at risk.

How it works

  1. 1A Linear webhook fires when an issue's due date is pushed out.
  2. 2The workflow traces the dependency chain from that issue to the designated launch milestone issue.
  3. 3It sums the slack along the critical path and subtracts the new slip.
  4. 4A branch checks whether remaining buffer has gone negative.
  5. 5If buffer remains, it logs and exits quietly.
  6. 6If the milestone is now at risk, it opens a PagerDuty incident with the cascade detail and posts an at-risk warning to the program channel in Microsoft Teams.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.