DEVOPS
Open a Discord deploy war-room thread on GitHub release
When a GitHub release is published, this opens a dedicated Discord thread, pins the release notes and rollout checklist.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- LogicSkip drafts and pre-releases
- ActionCreate Discord war-room threadDiscord
- ActionPin release notes + rollout checklistDiscord
- OutputMention on-call role in threadDiscord
What it does
Turns every published GitHub release into a live coordination thread in your deploys channel. The thread becomes the single source of truth for the rollout: release notes, the staged checklist, and who is driving.
When to use it
Use this when your team ships from GitHub Releases and wants a clean, per-release war-room instead of a noisy shared channel. Ideal for teams that run gated, multi-stage rollouts and need an audit trail of who acknowledged what.
How it works
- 1A GitHub `release.published` webhook fires with the tag, author, and notes.
- 2A logic step skips drafts and pre-releases unless they are explicitly tagged for canary.
- 3An action creates a Discord thread named after the release tag in the configured deploys channel.
- 4An action posts the formatted release notes plus a 4-stage rollout checklist (canary, 25%, 50%, 100%) as the pinned opening message.
- 5The output @-mentions the on-call role so the release owner is immediately notified in-thread.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DiscordCommunity channels + voice + bots.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.