DEVOPS

Slack-Approved Stale Flag Removal With Auto PR Stub

Posts each fully rolled-out, past-threshold flag to Slack with approve/skip buttons; on approval it opens a GitHub branch and draft PR stub that strips the flag references.

CategoryDevOps
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule starts the sweep
  • ActionCollect flags fully rolled out past thresholdHTTP webhook
  • ActionPost flags to Slack with approve/skipSlack
  • LogicBranch on human approval response
  • ActionCreate GitHub branch and draft PR stubGitHubGitHub
  • OutputReply in Slack thread with PR linkSlack

What it does

This workflow surfaces stale flags for a quick human decision in Slack. Each flag fully on past the threshold gets posted with approve and skip actions; approving kicks off a GitHub branch plus a draft PR that removes the flag's references, leaving an engineer to review and merge.

When to use it

Use it when you want a human checkpoint before any code change but still want the mechanical work pre-done. It avoids both blind auto-removal and the inertia of cleanup tasks that never get picked up.

How it works

  1. 1A daily schedule starts the sweep.
  2. 2An action collects flags fully rolled out past the threshold.
  3. 3An output posts each flag to Slack with approve/skip buttons.
  4. 4A logic step waits for and branches on the human response.
  5. 5On approval, an action creates a GitHub branch and a draft PR stub removing the flag references.
  6. 6The output replies in the Slack thread with the PR link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.