DEVOPS
Guard Production Promotion on Live Vitals
Intercepts a request to promote a staging deployment to production, runs a final synthetic Web Vitals and bundle check.
How it runs
The automated pipeline, trigger to output.
- TriggerPromotion request webhookHTTP webhook
- ActionRun synthetic vitals and bundle auditBrowserbase
- LogicEvaluate against production budgets
- ActionPromote deploy via Vercel API on passVercel
- ActionPage on-call on failPagerDuty
- OutputAnnounce outcome in release channelSlack
What it does
Adds a last-mile safety check before a build goes live. When someone requests promotion of a staging deployment to production, this workflow runs a final synthetic audit of Web Vitals and bundle size, and only calls the Vercel promote API if everything passes. If it fails, the promotion is held and on-call is paged.
When to use it
Use it when production promotions are manual and you want an automated final gate that prevents a regressed build from reaching customers, with a human escalation path when the gate trips.
How it works
- 1A promotion-request webhook fires with the candidate deployment ID.
- 2A browser step runs a synthetic Web Vitals and bundle audit against the staging URL.
- 3A logic step evaluates results against production budgets.
- 4On pass, an action calls the Vercel API to promote the deployment to production.
- 5On fail, a PagerDuty incident is opened for on-call with the failing metrics.
- 6Either outcome is announced in the release Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect VercelDeploys, runtime logs, analytics.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.