DEVOPS
PagerDuty Incident War Room Bootstrap
When a high-urgency PagerDuty incident is triggered, spin up a dedicated Slack channel, start a Zoom bridge, create a tracking Linear issue, and invite the on-call responders.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty high-urgency incident triggeredPagerDuty
- LogicConfirm urgency is high, skip otherwise
- ActionCreate and seed dedicated Slack incident channelSlack
- ActionStart Zoom bridge and pin join linkZoom
- ActionOpen Linear tracking issue linked to incidentLinear
- OutputInvite on-call responders to the channelSlack
What it does
Stands up a full incident war room the moment a major incident is declared. Instead of responders manually creating channels and bridges under pressure, this assembles the coordination surface automatically: a dedicated Slack channel, a live Zoom bridge, and a Linear tracking issue, all cross-linked and seeded with the incident details.
When to use it
Use it for SEV1/high-urgency incidents where minutes of setup overhead matter. It removes the scramble of 'who's making the channel' so responders go straight to fixing the problem.
How it works
- 1PagerDuty triggers a high-urgency incident and posts the webhook.
- 2Logic confirms the urgency is `high`; low-urgency incidents are skipped.
- 3A dedicated Slack channel is created and named from the incident ID, then seeded with the summary, service, and responder list.
- 4A Zoom meeting bridge is started and its join link is pinned in the channel.
- 5A Linear issue is opened to track timeline, owner, and follow-ups, linked back to the PagerDuty incident.
- 6The on-call and escalation responders are invited to the channel to begin coordination.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect ZoomMeetings, recordings, transcripts.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.