The flow
Starts it 1Logic 8Service 6
The steps in the order they run, from what starts it.
- 1Fetch Tasks from List 2Click UpService
- 2Scheduled 7 AM TriggerSchedule triggerStarts it
- 3Merge Task ListsMergeLogic
- 4Configure Task MonitoringSetLogic
- 5Deduplicate by Task IDRemove DuplicatesLogic
- 6Fetch Tasks from List 1Click UpService
- 7Filter Already 2nd Stale TasksFilterLogic
- 8Check First Stale Tag PresenceIfLogic
- 9Route by Stale TypeSwitchLogic
- 10If Date Not Updated for 2nd StaleIfLogic
- 11Add First Stale TagClick UpService
- 12Tag Task as 2nd StaleClick UpService
- 13Remove First Stale TagClick UpService
- 14No Operation NodeNo OpLogic
- 15Comment on 2nd Stale TaskClick UpService
How it's built
- Starts on
- A clock
- Steps
- 15, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- ClickUp
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own ClickUp 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. 15 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.
Before you run itNothing 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 15 steps before you point it at anything that matters.