DEVOPS
Escalate a flapping preview smoke gate to PagerDuty
On a scheduled cadence, re-runs smoke checks against open PRs' active previews and, when the same preview keeps failing, opens a PagerDuty incident for the owning on-call.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled re-check interval
- ActionList open PRs and preview URLsGitHub
- ActionSmoke-test each active previewHTTP webhook
- LogicFlag sustained repeat failures
- OutputOpen PagerDuty incident for on-callPagerDuty
What it does
Catches previews that stay broken instead of just failing once. On a schedule, it walks open pull requests, re-smoke-tests each one's live Vercel preview, and tracks repeat failures. When a preview has failed the gate across consecutive runs, it pages the responsible on-call through PagerDuty so a persistently red ephemeral environment becomes someone's problem before it stalls the release train.
When to use it
Use it when broken previews tend to linger unnoticed over a weekend or overnight, or when a flaky shared dependency repeatedly knocks previews offline and you want a human paged only after the failure is confirmed sustained — not on the first transient blip.
How it works
- 1A schedule fires the run at a fixed interval.
- 2A GitHub action lists open PRs and their head preview URLs.
- 3An HTTP step smoke-tests each active preview and records pass or fail.
- 4A logic branch flags previews failing for two or more consecutive runs.
- 5A PagerDuty action opens or updates an incident routed to the preview owner's on-call schedule.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.