The flow
Starts it 2Logic 10Service 8
The steps in the order they run, from what starts it.
- 1Every 60sSchedule triggerStarts it
- 2Daily 04:00Schedule triggerStarts it
- 3Get Active TorrentsHttp RequestService
- 4Extract SID + CutoffCodeLogic
- 5Find Bad PeersCodeLogic
- 6Get Recent BansData TableService
- 7Route by KindSwitchLogic
- 8Build Keep ListCodeLogic
- 9Build Ban RowCodeLogic
- 10Merge SlowMergeLogic
- 11Get Existing (Slow)Data TableService
- 12Overwrite qBit Ban ListHttp RequestService
- 13Upsert Peer RowData TableService
- 14Compute Strike RowCodeLogic
- 15Delete Old BansData TableService
- 16To Ban?FilterLogic
- 17Aggregate PeersCodeLogic
- 18Get Current PrefsHttp RequestService
- 19Build New Ban ListCodeLogic
- 20Set Prefs (Ban)Http RequestService
How it's built
- Starts on
- A clock
- Steps
- 20, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n 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. 20 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 20 steps before you point it at anything that matters.