DEVOPS
Announce a green preview gate and offer one-click promote in Slack
When a Vercel preview passes its smoke gate, posts a Slack message to the team channel summarizing the checks and tagging the PR author that the preview is verified and ready…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun smoke suite on preview URLHTTP webhook
- LogicContinue only if all checks passed
- ActionFetch PR title and authorGitHub
- OutputPost verified-preview summary to SlackSlack
What it does
Closes the loop on a passing gate by telling humans. After a preview clears its smoke checks, the workflow posts a rich Slack message to the engineering channel: the PR title, the preview URL, the checks that ran, and a mention of the author confirming the ephemeral environment is verified and safe to merge. Reviewers stop guessing whether the preview is good.
When to use it
Use it when smoke results live somewhere your team doesn't watch and approvals stall because nobody knows the preview is healthy. Best for teams that coordinate merges in Slack and want a clear, author-tagged go signal the moment a preview turns green.
How it works
- 1Vercel signals the preview deployment is ready.
- 2An HTTP step runs the smoke suite against the preview URL.
- 3A logic branch proceeds only when every check passed.
- 4A GitHub action enriches the message with PR title, author, and head SHA.
- 5A Slack action posts the verified-preview summary to the team channel, mentioning the author.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.