Block 1 - Docker Path
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.4
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow automates the process of checking for and applying updates to a self hosted n8n instance running on Docker. It runs on a schedule, checks for new versions, summarizes the...
n8n-nodes-base.set, n8n-nodes-base.ssh, n8n-nodes-base.httprequest, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, @n8n/n8n-nodes-langchain.chainllm
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Lucas Peyrin.
Original n8n.io sourceThis workflow automates the process of checking for and applying updates to a self-hosted n8n instance running on Docker. It runs on a schedule, checks for new versions, summarizes the release notes with AI, and asks for your approval via Telegram before updating.
Schedule node.latest or next).digest (a unique ID for an image version) of the running version against the latest available version for that tag.latest image is available), and an update is needed.docker compose command on your server, which pulls the new image, stops the old containers, and starts the new ones.Setup time: ~5-10 minutes
Get n8n Current Version and Update Docker nodes.Send a text message node.Google Gemini Chat Model node (or replace it with your preferred LLM node).Docker Path node. Set the docker_path to the absolute path of your docker-compose.yml file on the server (e.g., /root/n8n).worker_command to include the correct --scale argument for your setup. If not, you can leave it blank.Approve Update Telegram node and enter your personal Telegram Chat ID in the Chat ID field. This ensures the approval message is sent to you.To enable fully automatic updates (without manual approval): Delete the nodes from Get n8n Releases to Approved ? and connect the Needs Update ? node directly to the Update Docker node.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.
| Workflow | ๐ ๏ธ Auto n8n updater (Docker) |
|---|---|
| Complexity | advanced |
| Nodes | 26 |
| Categories | DevOps, AI Summarization |
| Author | Lucas Peyrin |
| Published | 24 Jun 2025 |
Use the JSON export at /data/workflows/5198/5198.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow automates the process of checking for and applying updates to a self hosted n8n instance running on Docker. It runs on a schedule, checks for new versions, summarizes the...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps, AI Summarization use case.