The flow
Starts it 2Logic 7Service 5
The steps in the order they run, from what starts it.
- 1Weekly Schedule TriggerSchedule triggerStarts it
- 2When clicking ‘Execute workflow’Manual triggerStarts it
- 3ConfigurationSetLogic
- 4Expand Repo ListCodeLogic
- 5Fetch All BranchesHttp RequestService
- 6Fetch Recently Merged PRsHttp RequestService
- 7Classify Branches, Merged vs StaleCodeLogic
- 8Auto-Delete Enabled?IfLogic
- 9Split Branches for DeletionCodeLogic
- 10Format Cleanup ReportCodeLogic
- 11Delete Single BranchHttp RequestService
- 12Send Report to SlackSlackService
- 13Summarize Deletion ResultsCodeLogic
- 14Send Cleanup Summary to SlackSlackService
How it's built
- Starts on
- A clock
- Steps
- 14, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.