Roll up PagerDuty alert storm into one Linear incident

During an outage, PagerDuty often fires dozens of related alerts that would otherwise spawn dozens of Linear tickets. This workflow detects an alert storm within a time window, opens one canonical Linear incident (or reuses an existing open one for the same service), and links every incoming alert to it while subscribing each responder named on the alerts.

Use it on services where a single failure cascades into many alerts. Instead of triaging duplicate tickets after the fact, you get one incident that accumulates context in real time and a subscriber list that already includes everyone paged.

1. 1A PagerDuty incident webhook triggers on each new alert.
2. 2The flow checks for an open Linear incident already tied to that PagerDuty service.
3. 3A branch decides: reuse the existing incident, or create a new canonical one.
4. 4It appends the alert details and links the PagerDuty incident to the Linear issue.
5. 5It adds every responder from the alert as a subscriber on the canonical issue.
6. 6It posts a running roll-up to the incident's Slack channel.