DEVOPS
Block Vercel promotion until preview smoke checks pass
When Vercel reports a preview deployment ready, runs a smoke-check suite against the preview URL and only promotes the deployment to production if every check passes.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun HTTP smoke checks against preview URLHTTP webhook
- LogicAll smoke checks passed?
- ActionPromote deployment to productionVercel
- OutputAlert deploy channel on failureSlack
What it does
This workflow turns every Vercel preview into a gated release candidate. The moment a preview finishes building, it hits the live preview URL with a battery of smoke checks (homepage 200, auth route, API health, a known data endpoint). Promotion to production only happens when all checks are green. Any failure stops the promotion and posts the exact failing check to Slack so an engineer can decide.
When to use it
Use it when you want automated preview QA but are not ready to fully auto-deploy. It is ideal for teams practicing continuous delivery who need a deterministic gate between "built" and "live" without a human clicking through every PR.
How it works
- 1Vercel fires a deployment.ready webhook for a preview build.
- 2The flow extracts the preview URL and deployment ID.
- 3It runs a sequence of HTTP smoke checks against that URL and scores pass/fail.
- 4A branch evaluates whether all checks passed.
- 5On pass, it calls the Vercel API to promote the deployment to production.
- 6On fail, it posts the failing check names and preview URL to the deploy Slack channel.
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 SlackChannels, DMs, threads, mentions.
- 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
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.