DEVOPS
Stale-flag owner nudge with auto-filed Linear cleanup tickets
On a schedule, identifies feature flags older than their intended lifespan, creates or updates a Linear cleanup ticket assigned to the flag owner.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers the aging check
- ActionFetch flags and expiry metadataHTTP webhook
- LogicSelect flags past expiry and compute overdue days
- ActionCreate or escalate the Linear cleanup ticketLinear
- OutputPost an aging comment mentioning the ownerLinear
What it does
Turns stale flags into tracked work. It scans flags for ones that have outlived a per-flag expiry date, then files a Linear ticket assigned to the flag owner with the flag key, age, and creation context. If a ticket already exists, it bumps the priority and adds an aging comment so ignored flags climb the backlog instead of being silently dropped.
When to use it
Use it when Slack pings get ignored and you need flag cleanup to live where the rest of engineering work does. Best for teams that plan in Linear and want stale flags to age into visible, prioritized tickets.
How it works
- 1A schedule triggers the aging check.
- 2An HTTP call retrieves flags plus each flag's expiry metadata.
- 3A logic step selects flags past expiry and computes how overdue each is.
- 4Linear creates a cleanup ticket, or finds the existing one and raises its priority.
- 5The final step posts an aging comment with the flag owner @-mentioned for accountability.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.