DEVOPS
Reconcile orphaned flags between codebase and provider
On a schedule, cross-references flag keys referenced in the GitHub codebase against the flags defined in the provider, then reports orphans both ways.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule starts the reconciliation
- ActionSearch the repo for referenced flag keysGitHub
- ActionFetch all flags defined in the providerHTTP webhook
- LogicDiff into defined-but-unused and used-but-undefined
- OutputPost the categorized drift report to SlackSlack
What it does
Finds the two kinds of flag drift. It searches the GitHub repo for every flag key referenced in code, pulls the full flag list from your provider, and diffs the two sets. Flags defined in the provider but absent from code are dead and safe to archive; flag keys used in code but missing from the provider are landmines that will evaluate to a default. It compiles both lists into one triage report.
When to use it
Use it when you suspect your flag dashboard and your codebase have quietly diverged, especially after big refactors or provider migrations. It is a read-only auditor — it diagnoses drift rather than changing anything.
How it works
- 1A schedule starts the reconciliation.
- 2GitHub code search collects every flag key referenced across the repo.
- 3An HTTP call fetches all flags defined in the provider.
- 4A logic step diffs the two sets into defined-but-unused and used-but-undefined buckets.
- 5Slack posts a categorized drift report to the triage channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.