DEVOPS
Post Vercel preview smoke results as a PR comment
On each new Vercel preview deployment, runs a smoke suite and edits a single sticky comment on the GitHub PR with a live checklist of which routes passed or failed.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun smoke checks on preview routesHTTP webhook
- LogicSticky comment already exists?
- OutputCreate or edit PR smoke commentGitHub
What it does
This workflow gives reviewers an at-a-glance QA summary right inside the pull request. When a preview deploys, it runs a smoke suite across your critical routes and renders the results as a markdown checklist. Instead of spamming the thread, it maintains one sticky comment per PR and edits it on every redeploy, so the comment always reflects the latest preview.
When to use it
Use it when your team reviews PRs in GitHub and wants smoke status visible without leaving the page. It complements a hard merge gate by giving humans the readable detail behind a pass or fail.
How it works
- 1Vercel fires a deployment.ready webhook for a preview build.
- 2The flow runs HTTP smoke checks against the preview URL and collects per-route results.
- 3It looks up the PR by branch and searches for an existing sticky smoke comment.
- 4A branch decides whether to create a new comment or edit the existing one.
- 5It writes the markdown checklist with the preview URL and timestamp to the PR.
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.