The flow
Starts it 1Logic 6Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get Current n8n VersionSshService
- 3Get Local Image DigestSshService
- 4Get Remote Image DigestHttp RequestService
- 5Prepare Update DataSetLogic
- 6If No ChangesIfLogic
- 7No UpdatesNo OpLogic
- 8Ask For Approval to UpdateEmail SendService
- 9If ApprovedIfLogic
- 10Check Existence of Update ScriptSshService
- 11Do NothingNo OpLogic
- 12If File ExistsIfLogic
- 13Execute Update ScriptSshService
- 14Create Update ScriptSshService
How it's built
- Starts on
- A clock
- Steps
- 14, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Email
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email 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.