DEVOPS

Auto-spin a Zoom war-room when PagerDuty hits SEV-1

When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…

CategoryDevOps
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPagerDuty incident escalatedPagerDutyPagerDuty
  • LogicProceed only if SEV-1 / P1
  • ActionCreate Zoom war-room meetingZoomZoom
  • ActionAdd bridge note to PagerDuty incidentPagerDutyPagerDuty
  • OutputPost pinned bridge link to SlackSlack

What it does

The moment PagerDuty fires a SEV-1 (or P1) incident, this workflow creates a fresh Zoom meeting branded with the incident ID and drops the join link into the right Slack channel. No one has to scramble to start a bridge during the worst minutes of an outage.

When to use it

Use it when your on-call rotation lives in PagerDuty and you want a live voice bridge to exist automatically for every critical incident — without an engineer fumbling to schedule a call mid-page.

How it works

  1. 1A PagerDuty webhook fires on incident escalation.
  2. 2A filter checks the urgency/priority and only proceeds for SEV-1 / P1 incidents, ignoring lower-severity noise.
  3. 3Zoom creates an instant meeting titled with the incident number and a 4-hour window.
  4. 4The workflow writes the incident summary and bridge details back to PagerDuty as a note.
  5. 5Slack posts the join link, dial-in, and incident title to the incident channel, pinned for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PagerDutyIncidents, on-call, escalations.
  2. 2
    Connect ZoomMeetings, recordings, transcripts.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.