DEVOPS
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.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack slash command declares incidentSlack
- ActionCreate Zoom war-room bridgeZoom
- ActionPull recent Sentry errors for serviceSentry
- ActionCreate Linear tracking issueLinear
- OutputReply in Slack thread with linksSlack
What it does
Sometimes you know there's an incident before any monitor fires. This workflow lets any engineer type a Slack slash command to instantly stand up a Zoom war-room, create a Linear tracking issue, and pull recent Sentry errors for the named service into the thread — all without leaving Slack.
When to use it
Use it for human-declared incidents: a customer report, a gut-feel degradation, or a planned risky change where you want a bridge ready. It gives operators a one-line way to formalize a war-room and start a paper trail.
How it works
- 1A Slack slash command (with the service name and a short description) triggers the workflow.
- 2Zoom creates an incident bridge titled with the declared service.
- 3The workflow queries Sentry for recent unresolved issues on that service to attach as context.
- 4Linear creates a tracking issue tagged as an incident with the bridge link in the description.
- 5Slack replies in-thread with the Zoom join link, the Linear ticket URL, and the top Sentry errors.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect ZoomMeetings, recordings, transcripts.
- 3Connect SentryErrors, performance, releases.
- 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.