Automatic self-hosted application updates with Coolify deployments
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs on a schedule (every day) (plus 1 other trigger). It uses only n8n's built-in nodes. It also calls api.github.com and app.coolify.io over HTTP.
How it runs
Trigger: On a schedule (every day) (plus 1 other trigger).
- CALL YOUR N8N INSTANCE and retrieve the version (HTTP Request): calls an HTTP API
- CALL GITHUB and retrieve the last n8n image stable version (HTTP Request): calls api.github.com
- Merge: merges the data from its input branches
- Rename variable and unify format (Edit Fields (Set)): sets 2 fields: actualn8nversion, newn8nversion
- If: checks a condition and branches into true / false
- CALL COOLIFY OR SIMILAR SERVICE FOR UPDATE IMAGE (HTTP Request): calls app.coolify.io
HTTP calls to: api.github.com, app.coolify.io
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - No Operation, do nothing
n8n-nodes-base.noOp - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Manual Trigger
n8n-nodes-base.manualTrigger
From the author
Auto-update n8n instance with Coolify Who’s it for This workflow is designed for self-hosted n8n administrators who want to keep their instance automatically updated to the latest stable release. It removes the need for manual version checks and ensures…