DEVOPS
Monthly DORA Executive Report to Notion
On the first of each month, compiles every team's deploy frequency and lead-time trend from the BigQuery scorecard and publishes a formatted month-over-month executive report…
How it runs
The automated pipeline, trigger to output.
- TriggerFirst-of-month schedule
- ActionQuery last two months of scorecard rowsBigQuery
- LogicCompute month-over-month deltas and trend class
- LogicRender report body with summary table
- OutputPublish dated report page to NotionNotion
What it does
This builds a human-readable monthly DORA summary for leadership. It reads the accumulated warehouse scorecard, computes month-over-month deltas per team, and writes a clean narrative report into a Notion database.
When to use it
Use it when engineering leaders want a recurring, no-effort delivery-health briefing they can read in Notion — pairing the raw warehouse numbers with plain-language trend callouts and improvement flags.
How it works
- 1A first-of-month schedule triggers the run.
- 2An action queries the BigQuery `dora_team_scorecard` table for the last two months of per-team rows.
- 3A compute step calculates each team's deploy-frequency and lead-time change versus the prior month and classifies the direction as improving, flat, or regressing.
- 4A formatting step assembles a report body with a summary table and one bullet per team highlighting the biggest mover.
- 5The output step creates a dated page in the Notion DORA reports database with the rendered summary, ready to share with stakeholders.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect NotionPages, databases, comments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.