DEVOPS
Weekly DORA tier classifier with PagerDuty escalation for laggards
Weekly, reads the assembled DORA metrics from BigQuery, classifies each team into Elite/High/Medium/Low tiers, posts the ranking to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionQuery 7-day DORA aggregates from BigQueryBigQuery
- LogicClassify teams into DORA tiers, flag regressions
- OutputPost tiered leaderboard to SlackSlack
- LogicBranch on Low-tier teams
- ActionOpen PagerDuty review for laggardsPagerDuty
What it does
Turns raw DORA numbers into accountable signal. It reads the past week's deploy-frequency and lead-time aggregates from BigQuery, scores each team against the standard DORA performance bands, and routes outcomes: a leaderboard to Slack for everyone, and a tracked PagerDuty incident for any team that dropped into the Low tier so the regression gets an owner.
When to use it
Use this when you already have a DORA metrics table in BigQuery and want the org to act on it weekly rather than just look at a dashboard. Good for platform teams driving delivery-performance accountability.
How it works
- 1A weekly Monday schedule trigger starts the run.
- 2Query the rolling 7-day per-team DORA aggregates from BigQuery.
- 3Logic step assigns each team an Elite/High/Medium/Low tier and flags week-over-week regressions.
- 4Post the tiered leaderboard to Slack.
- 5Branch: for any team in the Low tier, open a PagerDuty incident tagged with the regression details.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.