DEVOPS
Trigger rollback and page on-call from a Discord war-room command
Lets an engineer type a /rollback slash command in the deploy thread to revert the last Vercel deployment and open a PagerDuty incident.
How it runs
The automated pipeline, trigger to output.
- TriggerDiscord /rollback slash commandDiscord
- LogicVerify authority + active deploy
- ActionRevert to last good Vercel deployVercel
- ActionOpen PagerDuty incidentPagerDuty
- OutputConfirm rollback in threadDiscord
What it does
Gives the war-room a panic button. An authorized engineer runs `/rollback` inside the deploy thread and the workflow reverts production and escalates, all without leaving Discord.
When to use it
Use this for fast incident response during a bad rollout, when seconds matter and you want one command to both revert traffic and wake the right people, rather than juggling three dashboards.
How it works
- 1A Discord slash-command trigger fires when someone runs `/rollback` in a deploy thread.
- 2A logic step verifies the invoker holds the deploy-authority role and that an active deployment exists.
- 3An action calls Vercel to promote the previous known-good deployment back to production.
- 4An action opens a PagerDuty incident tagged with the failed release and links the Discord thread.
- 5The output posts a confirmation in the thread with the reverted revision, incident link, and who triggered it.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.