DEVOPS
Weekly DORA Scorecard Digest with Regression Alert
Every Monday, reads the week's deploy-frequency and lead-time figures from Snowflake, posts a formatted scorecard to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerMonday 08:00 schedule
- ActionQuery this-week vs last-week DORA aggregatesSnowflake
- LogicCompute deltas and flag sharp regressions
- OutputPost scorecard with trend arrows to SlackSlack
- ActionOpen PagerDuty incident for flagged teamsPagerDuty
What it does
This workflow closes the DORA loop by reporting it. Each Monday it reads the trailing week's deploy-frequency and lead-time-for-changes aggregates from Snowflake, builds a readable scorecard, and posts it to your engineering Slack channel. If lead time spiked or deploy frequency dropped beyond a threshold, it raises a PagerDuty incident so the regression gets owned, not buried.
When to use it
Use it for a standing Monday engineering review or to keep leadership honest on delivery health. Best when your DORA metrics already land in Snowflake and you want push-based reporting plus an early-warning signal.
How it works
- 1A schedule fires every Monday at 08:00.
- 2The flow runs a Snowflake query returning this week's and last week's deploy count and median lead time per team.
- 3A logic step computes week-over-week deltas and flags teams whose lead time rose over 30 percent or whose deploys fell over 40 percent.
- 4It posts the full scorecard with trend arrows to Slack.
- 5If any team is flagged, it opens a PagerDuty incident tagged to that team's service.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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.