The flow
Starts it 2Logic 4Service 3
The steps in the order they run, from what starts it.
- 1Schedule every time you want start the update checkSchedule triggerStarts it
- 2When clicking ‘Execute workflowManual triggerStarts it
- 3CALL YOUR N8N INSTANCE and retrieve the versionHttp RequestService
- 4CALL GITHUB and retrieve the last n8n image stable versionHttp RequestService
- 5Merge bot data and pass just what we needMergeLogic
- 6Rename variable and unify formatSetLogic
- 7If the 2 versions is not the same make an update of imageIfLogic
- 8CALL COOLIFY OR SIMILAR SERVICE FOR UPDATE IMAGEHttp RequestService
- 9No Operation, do nothingNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 9, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- 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. 9 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 9 steps before you point it at anything that matters.