DEVOPS
On-Demand DORA Snapshot for a Single Team
Triggered manually with a team and date range, pulls that team's GitLab deploys and lead times, writes the detailed records to Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with team and date range
- ActionFetch team pipelines and MRs in the windowGitLab
- LogicBuild per-deploy rows and aggregate summary
- ActionWrite detailed records to PostgresPostgres
- OutputAppend snapshot summary to BigQueryBigQuery
What it does
This produces a focused DORA snapshot for one team over any window you specify. It captures both the granular per-deploy records and a rolled-up summary, supporting deep dives like quarterly reviews or post-reorg baselining.
When to use it
Use it when someone asks "how is Team X actually doing" outside the normal weekly cadence — a manager prepping a review, or validating a process change against a specific historical period.
How it works
- 1A manual trigger collects the team identifier and a start/end date range.
- 2An action queries the GitLab API for that team's pipelines and merged MRs within the window.
- 3A compute step builds per-deploy rows (deploy time, lead-time hours, MR id) plus a single aggregate summary of deploy count and median lead time.
- 4The detailed rows are written to a Postgres `dora_deploy_events` table for record-level analysis.
- 5The output step appends the aggregate summary to the BigQuery scorecard table, tagged as an on-demand snapshot so it does not mix with the scheduled weekly series.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect BigQueryDatasets, queries, schemas.
- 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.