DEVOPS
Stale-flag debt to Linear cleanup tickets grouped by owner
Detects feature flags fully rolled out for 90+ days and creates one Linear issue per flag owner listing their stale flags, so cleanup work lands in each team's backlog.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule
- ActionQuery stale flags with ownersPostgres
- LogicGroup rows by owner
- ActionCreate Linear cleanup issue per ownerLinear
- OutputNotify owners in SlackSlack
What it does
Finds feature flags that have been fully rolled out for 90 days or more, groups them by their registered owner, and creates a single Linear issue per owner that itemizes every stale flag they are responsible for, with key, age, and code locations.
When to use it
Use it when you want flag cleanup tracked as real backlog work rather than ad-hoc MRs. Grouping by owner keeps each engineer's queue tidy and gives managers a clean view of who carries the most flag debt.
How it works
- 1A schedule triggers the run on the first of each month.
- 2A Postgres query returns all flags at 100% rollout older than 90 days, including owner and reference paths.
- 3A logic step groups the rows by owner email and skips owners with zero stale flags.
- 4For each owner group, a Linear action creates an issue assigned to that owner, titled with the flag count and listing each flag as a checklist item.
- 5A Slack DM-style channel post notifies each owner that their cleanup issue is ready, linking the Linear ticket.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.