DEVOPS
Page on-call when a Vercel production-track preview fails QA
Watches Vercel preview deployments on the release branch, runs smoke checks, and if checks fail it opens a PagerDuty incident with the failing routes and links a Linear ticket…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- LogicOn release-track branch and checks failed?
- ActionOpen PagerDuty incidentPagerDuty
- OutputFile linked Linear regression ticketLinear
What it does
This workflow treats QA failures on your release branch as incidents. When a preview built from the release-track branch finishes, it runs smoke checks against the preview URL. A failure does not just post a message that scrolls away. It opens a PagerDuty incident to page the on-call engineer and files a Linear ticket capturing the failing routes, the deployment ID, and the preview link.
When to use it
Use it for the branch that feeds production, where a broken preview means a release is about to be blocked. The PagerDuty page guarantees someone responds; the Linear ticket guarantees the failure is tracked to resolution.
How it works
- 1Vercel fires a deployment.ready webhook for a preview build.
- 2A branch filters to deployments on the configured release-track branch only.
- 3The flow runs smoke checks against the preview URL.
- 4If any check fails, it opens a PagerDuty incident with the failing-route summary.
- 5It then creates a linked Linear ticket so the regression has a clear owner.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.