DEVOPS
Stale Feature-Flag Sweep to ClickUp Cleanup Tasks
Runs weekly across your feature-flag service, finds flags that have been fully rolled out (100% on) for longer than a set threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the sweep
- ActionFetch all flags and rollout stateHTTP webhook
- LogicFilter to flags 100% on past threshold
- LogicDrop flags that already have a cleanup task
- ActionCreate ClickUp cleanup task per stale flagClickUp
- OutputPost sweep summary to SlackSlack
What it does
On a weekly schedule, this workflow pulls every active feature flag, identifies the ones serving a single variant to 100% of traffic for more than N days, and files one ClickUp task per stale flag so engineers can delete the flag and its dead code path.
When to use it
Use it when your flag count keeps climbing and nobody circles back to retire flags after a rollout finishes. It turns silent flag debt into tracked, assignable cleanup work without anyone manually auditing the flag dashboard.
How it works
- 1A weekly schedule fires the sweep.
- 2An action fetches all flags and their rollout state from the flag platform.
- 3A logic step keeps only flags at 100% on a single variant with a last-changed date older than the threshold.
- 4A logic step deduplicates against flags that already have an open cleanup task.
- 5An action creates a ClickUp task per remaining flag, tagged with owner, flag key, and age.
- 6The output posts a summary count to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.