DEVOPS
Vercel Preview Smoke Gate with PR Checklist
When Vercel finishes a preview deployment for a pull request, runs a scripted set of HTTP smoke checks against the preview URL and posts a pass/fail checklist as a GitHub PR…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- LogicKeep only preview builds on an open PR
- ActionRun HTTP smoke checks against preview URLHTTP webhook
- LogicRoll checks into pass/fail verdict
- OutputPost checklist comment and set qa-gate commit statusGitHub
What it does
Turns every Vercel preview into a self-testing gate. The moment a preview build goes live, this workflow hits the preview URL with a list of smoke checks (homepage 200, login route, health endpoint, a known API response) and writes the results back to the pull request as a tidy checklist comment plus a `qa-gate` commit status.
When to use it
Use it when a green Vercel build is not enough proof a branch is safe to merge and you want a fast, automated first pass before a human reviews. Best for teams that already require status checks on protected branches.
How it works
- 1Vercel fires a deployment-succeeded webhook carrying the preview URL and the source commit SHA.
- 2A filter keeps only `preview` deployments tied to an open PR and drops production builds.
- 3An HTTP step runs each smoke check against the preview URL and records status code and latency.
- 4Logic rolls the results into a single pass/fail verdict.
- 5A GitHub action posts the checklist comment and sets the `qa-gate` commit status to success or failure, which the branch protection rule enforces at merge time.
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
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.