DEVOPS
Page on-call when a Vercel preview breaks a critical path
Watches Vercel preview deployments, re-runs the critical-path smoke suite, and raises a PagerDuty incident plus a Slack alert only when a previously-passing path regresses.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment webhookVercel
- ActionRun critical-path smoke suite on previewBrowserbase
- LogicDiff results against branch last-good baseline
- ActionOpen PagerDuty incident on regressionPagerDuty
- OutputMirror incident to Slack channelSlack
What it does
This workflow treats preview deployments as an early-warning system. After each preview deploy it runs the critical-path smoke suite, compares results to the last known-good run for that branch, and escalates only when a path that used to work now fails - reducing alert noise to genuine regressions.
When to use it
Use it on high-traffic projects where a regression caught at preview is far cheaper than one caught in production, and where the team already runs PagerDuty for on-call.
How it works
- 1A Vercel deployment webhook delivers the preview URL and branch.
- 2Browserbase runs the smoke suite against the preview and records per-path status.
- 3A logic step diffs the current results against the stored last-good baseline for the branch.
- 4If no path regressed, the run ends quietly and the baseline is updated.
- 5If a path regressed, a PagerDuty incident is opened with the failing path, branch, and screenshot.
- 6A Slack message mirrors the incident into the team channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.