Automated Buildkite Pipeline Registry Sync
Every morning, WebRun opens Buildkite, checks every pipeline's latest build status and last run date, reconciles that against an Airtable registry of pipelines your team is supposed to be running, and updates a Notion CI health page flagging any pipeline that hasn't run in 30 days or looks abandoned.
How do I keep my Buildkite pipeline registry accurate?
WebRun checks every Buildkite pipeline every morning for its latest status and last run date, reconciling that against an Airtable pipeline registry. It updates a Notion CI health page and flags any pipeline that hasn't run in 30 days, so the registry stays honest and abandoned pipelines don't go unnoticed.
- The pipeline registry never drifts out of sync with what actually exists
- Abandoned pipelines get flagged instead of running unnoticed
- CI health is visible on one page instead of scattered across pipelines
Built for DevOps teams · platform engineers · release engineers · engineering managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
buildkite.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Buildkite - check every pipeline's latest status
- Open Buildkite and list every pipeline with its latest build status
- Capture the last run date for each pipeline
- Flag any pipeline with no run in 30 days or more
Done when Every pipeline is listed with its latest status and last run date.
-
2
Airtable - reconcile against the pipeline registry
airtable.com
WebRun opens Airtable to reconcile against the pipeline registry. - Reconcile the live pipeline list against the Airtable pipeline registry
- Add any pipeline found in Buildkite but missing from the registry
- Flag any registry entry whose pipeline no longer exists
Done when The Airtable registry matches the pipelines that actually exist in Buildkite.
-
3
Notion - update the CI health page
notion.so
WebRun opens Notion to update the CI health page. - Update the CI health page with each pipeline's current status
- List pipelines flagged as possibly abandoned separately
- Keep the page as the current source of truth for CI health
Done when The Notion page reflects every pipeline's current status and flags abandoned ones.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete or disable a pipeline?
No. WebRun only reports and reconciles records. Removing or disabling a pipeline is always a decision your team makes in Buildkite.
What counts as abandoned?
A pipeline with no run in 30 days or more. It's flagged for someone to check whether it's still needed, not removed automatically.
What if a new pipeline was added outside Airtable?
It gets added to the Airtable registry automatically on the next run, so the registry never falls behind what actually exists.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.