DEVOPS
Slack Slash-Command Incident War Room Spin-Up
An engineer types a Slack command to declare an incident, and the workflow spins up a dedicated channel, pages the on-call via PagerDuty, and opens a Zoom bridge.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer runs /incident slash commandSlack
- ActionCreate dedicated incident Slack channelSlack
- ActionPage on-call commander via PagerDutyPagerDuty
- ActionOpen Zoom incident bridgeZoom
- OutputPin summary with links in incident channelSlack
What it does
This workflow lets any engineer declare an incident from Slack with a single slash command. It instantly creates a dedicated incident channel, pages the on-call lead through PagerDuty, opens a Zoom bridge for live response, and pins the key links so the whole team converges in one place without manual coordination.
When to use it
Use it when declaring an incident today means manually creating a channel, hunting for the on-call, and starting a call — losing precious minutes. Best for teams that want a consistent, one-command incident kickoff with a real-time bridge.
How it works
- 1An engineer runs the `/incident` slash command in Slack with a short description.
- 2The workflow creates a dedicated `#incident-<timestamp>` Slack channel.
- 3It triggers a PagerDuty incident to page the on-call incident commander.
- 4It opens a Zoom meeting and captures the join link.
- 5It posts and pins a summary in the new channel with the PagerDuty and Zoom links.
- 6The final step DMs the declaring engineer the channel link to confirm spin-up.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect ZoomMeetings, recordings, transcripts.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.