ENGINEERING
Vercel preview QA gate that sets a GitHub commit status
Runs a multi-route smoke suite against a fresh Vercel preview and writes a pass/fail commit status check back to the GitHub PR so merge can be blocked until the preview is…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionProbe critical routes over HTTPHTTP webhook
- LogicAggregate route results into pass/fail
- ActionSet GitHub commit status checkGitHub
- OutputComment broken routes on PR if failedGitHub
What it does
When a Vercel preview deploy goes live, this workflow probes several critical routes, then posts a GitHub commit status check (success or failure) on the head commit of the associated pull request. That status becomes a required check, so the PR can't merge until the preview passes.
When to use it
Use it when you want preview verification to be a hard merge gate, not just an FYI. Ideal for teams enforcing branch protection who want automated preview health as a required status.
How it works
- 1A Vercel deployment-ready webhook supplies the preview URL and Git commit SHA.
- 2The flow runs HTTP requests against a configured list of critical routes (home, login, API health).
- 3A logic step aggregates the results — all routes must return 2xx to pass.
- 4The workflow calls the GitHub Statuses API to set a `preview/qa-gate` check on the commit, success or failure, with a target link to the preview.
- 5On failure it also adds a PR comment listing exactly which routes broke.
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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.