DEVOPS
Block PR merge when the Vercel preview fails smoke tests
When a Vercel preview deployment finishes, runs an HTTP smoke suite against the ephemeral URL and sets a GitHub commit status that blocks merge if any check fails.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- LogicKeep only successful preview builds
- ActionRun HTTP smoke checks against preview URLHTTP webhook
- LogicEvaluate pass/fail from responses
- OutputPost commit status to gate mergeGitHub
What it does
Turns every Vercel preview deployment into a hard merge gate. As soon as a preview is ready, it hits the live ephemeral URL with a battery of smoke checks (homepage 200, health endpoint, a critical API route) and reports the verdict back to the pull request as a required commit status. A broken preview can no longer be merged.
When to use it
Use it when your team merges to a trunk that auto-deploys to production and you want a real, running-environment check — not just unit tests — to stand between a bad preview and main. Pair it with a GitHub branch protection rule that requires the `preview-smoke` status.
How it works
- 1Vercel fires a deployment webhook when the preview reaches the ready state.
- 2A filter keeps only `preview` targets that succeeded, discarding production and errored builds.
- 3An HTTP step calls the preview URL's smoke endpoints and collects status codes and latencies.
- 4A logic branch decides pass or fail based on the responses.
- 5A GitHub commit status is posted (`success` or `failure`) against the PR's head SHA, gating the merge button.
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.
- 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.