DEVOPS
Nightly Deploy Frequency Rollup to Engineering Scorecard
Each night, count the day's production deployments per GitHub repository and append the totals to a Notion engineering scorecard so the team sees deploy frequency without manual…
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule at 23:30
- ActionFetch production Deployment events (last 24h)GitHub
- LogicKeep only deployments with success status
- LogicGroup and count deploys per repository
- OutputUpsert dated deploy-frequency rows in Notion scorecardNotion
What it does
Every night this workflow pulls the day's GitHub Deployment events for your production environment, counts successful deploys per repository, and writes a dated row into a Notion scorecard database. It turns raw deployment activity into the DORA deploy-frequency metric your leadership already tracks, with zero spreadsheet upkeep.
When to use it
Use it when you want a reliable daily deploy-frequency number per service but don't want engineers exporting CSVs or eyeballing the Actions tab. Ideal for teams formalizing DORA reporting or prepping weekly engineering reviews.
How it works
- 1A nightly schedule fires at 23:30 in your release timezone.
- 2The flow queries the GitHub Deployments API for each tracked repo, filtered to the `production` environment and the last 24 hours.
- 3A logic step keeps only deployments whose latest status is `success`, discarding failed or in-progress ones.
- 4It groups the survivors by repository and computes a per-repo count plus an org-wide total.
- 5The final step upserts a dated row per repo into the Notion scorecard database, so the table grows one clean entry per service per day.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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
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.