Skip to main content

๐Ÿ› ๏ธ Auto n8n updater (Docker)

Workflow preview

Workflow preview
100%
๐Ÿ› ๏ธ Auto n8n updater (Docker) preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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...

Best for

  • DevOps automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

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

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Lucas Peyrin.

Original n8n.io source

1.1 Workflow description

Title
๐Ÿ› ๏ธ Auto n8n updater (Docker)
Workflow name
๐Ÿ› ๏ธ Auto n8n updater (Docker)

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 release notes with AI, and asks for your approval via Telegram before updating.

  1. Scheduled Check: The workflow runs hourly, triggered by a Schedule node.
  2. Version Discovery:
    • It first confirms it's running in a Docker environment.
    • It uses SSH to connect to the host machine and inspects the running n8n container to find its current version tag (e.g., latest or next).
    • It then queries the Docker Hub API to compare the image digest (a unique ID for an image version) of the running version against the latest available version for that tag.
  3. Update Detection: If the digests do not match, it means a new image has been pushed for your version tag (e.g., a new latest image is available), and an update is needed.
  4. AI-Powered Release Notes:
    • It fetches the official release notes for the new version from the GitHub API.
    • An AI model (LLM) summarizes these technical notes into a concise, human-readable overview of the key features and fixes.
  5. Manual Approval: It sends a message to a Telegram chat with the AI-generated summary and two buttons: "โœ… Update" and "โŒ Ignore". The workflow then pauses and waits for your response.
  6. Execute Update: If you approve the update, the workflow uses SSH to run a docker compose command on your server, which pulls the new image, stops the old containers, and starts the new ones.

Set up steps

Setup time: ~5-10 minutes

  1. SSH Credentials:
    • Go to Credentials and create a new SSH credential with the username, host, and password/private key for the server where your n8n Docker instance is running.
    • Select this credential in the Get n8n Current Version and Update Docker nodes.
  2. Telegram Bot Credentials:
    • Create a Telegram Bot and get its API token.
    • Go to Credentials and create a new Telegram credential with your bot's token.
    • Select this credential in the Send a text message node.
  3. AI Model Credentials:
    • Ensure you have credentials for an AI provider (like Google AI, OpenAI, etc.) set up.
    • Select your desired credential in the Google Gemini Chat Model node (or replace it with your preferred LLM node).
  4. Configure Paths and Commands:
    • Open the Docker Path node. Set the docker_path to the absolute path of your docker-compose.yml file on the server (e.g., /root/n8n).
    • If you use workers, adjust the worker_command to include the correct --scale argument for your setup. If not, you can leave it blank.
  5. Set Your Chat ID:
    • Open the 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.
  6. Activate the workflow. It will now check for updates every hour.

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.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Docker Path

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 2 - Update Docker

Type / Role
n8n-nodes-base.ssh - ssh
Config choices
Version 1

Block 3 - Get n8n Current Version

Type / Role
n8n-nodes-base.ssh - ssh
Config choices
Version 1

Block 4 - Get Instance's Settings

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 5 - Is Docker

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 6 - Get Version's Last Update

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Target Version

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Get Current Version

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 9 - Needs Update ?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 10 - Google Gemini Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 11 - Approved ?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 12 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Every Hour

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 14 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Release Overview

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 19 - Approve Update

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 20 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Get n8n Github Release

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 24 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow ๐Ÿ› ๏ธ Auto n8n updater (Docker)
Complexity advanced
Nodes 26
Categories DevOps, AI Summarization
Author Lucas Peyrin
Published 24 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5198/5198.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does ๐Ÿ› ๏ธ Auto n8n updater (Docker) do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.