DEVOPS
Auto-quarantine flaky e2e tests that page on-call and notify Teams
Triggered when a PagerDuty incident fires from a known-flaky end-to-end test alert, auto-applies a quarantine label in GitHub, resolves the page.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggeredPagerDuty
- LogicConfirm alert maps to a flake-suspect test
- ActionApply quarantine label to GitHub issueGitHub
- ActionResolve PagerDuty incident with notePagerDuty
- OutputPost action summary to Microsoft TeamsMicrosoft Teams
What it does
This workflow stops flaky end-to-end tests from waking up on-call. When PagerDuty raises an incident whose alert maps to a test already marked flake-suspect, it applies a quarantine label to the test's GitHub tracking issue, auto-resolves the low-signal page with a note, and announces the action in a Microsoft Teams channel so the team still has visibility without the 3 a.m. interruption.
When to use it
Use it when intermittent e2e tests generate pager noise faster than your team can fix them, and you want a safe, logged way to suppress the page while keeping the work tracked.
How it works
- 1PagerDuty fires an incident-triggered event into the workflow.
- 2A filter confirms the alert key matches a test on the flake-suspect list.
- 3The workflow applies the quarantine label to the corresponding GitHub issue.
- 4It resolves the PagerDuty incident with an automated quarantine note and links the issue.
- 5It posts a summary card to Microsoft Teams naming the test and the action taken.
- 6The resolved incident ID and issue link are returned as output.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.