Skip to main content

Automate docker container updates with Telegram approval system

Workflow preview

Workflow preview
100%
Automate docker container updates with Telegram approval system preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Who is this for? This workflow is for DevOps engineers, system administrators, and Docker users who want to automate the process of checking for updates, verifying them, and applying updates to the...

Best for

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

Tools used

n8n-nodes-base.ssh, n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.stickynote, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.merge, n8n-nodes-base.if

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Automate docker container updates with Telegram approval system
Workflow name
Automate docker container updates with Telegram approval system
Who is this for?

This workflow is for DevOps engineers, system administrators, and Docker users who want to automate the process of checking for updates, verifying them, and applying updates to their Docker-based deployment in a controlled manner. For example, this workflow is used to update the n8n Docker image.

What does this workflow do?
  • Fetches the latest Docker image version from GitHub.
  • Compares it with the currently running version on the server.
  • Sends a Telegram message requesting confirmation if an update is available.
  • If confirmed, pulls the latest n8n Docker image, updates the container, and restarts it.
  • Sends a Telegram message confirming the update is completed.
  • Schedules automatic checks, Uses a cron trigger in n8n to check for updates at regular intervals.
Setup
  • Ensure n8n is installed and running in a Docker container.
  • Create a Telegram bot using BotFather.
  • Set up Telegram credentials.
  • Set up SSH credentials (ensure the SSH user has sudo access).
  • Obtain the bot token and chat ID.
  • Set the Default variable node
    • telegram-id (You can find it by messaging @get_id_bot).
    • n8n-container-name (Specify the name of the n8n container.)
    • working-directory (The directory where your docker-compose.yml is).
  • You can use a manual trigger or a schedule trigger to update (for n8n, I use Cron every 3 days to check for a new version).
How to customize this workflow
  • Change the update mechanism: Modify the Docker commands if using a different container runtime or orchestration tool.
  • Modify the confirmation flow: Add extra validation steps, such as checking for breaking changes before updating.
  • Use a different notification method: Replace Telegram with Slack, email, or another notification service.

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 - Pull n8n Image

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

Block 2 - docker compose pull

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

Block 3 - check n8n installed version

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

Block 4 - When clicking ‘Test workflow’

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

Block 5 - Schedule Trigger

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

Block 6 - Sticky Note

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

Block 7 - Sticky Note1

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

Block 8 - Sticky Note2

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

Block 9 - Sticky Note3

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

Block 10 - Sticky Note4

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

Block 11 - Sticky Note5

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

Block 12 - Sticky Note6

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

Block 13 - Sticky Note7

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

Block 14 - Sticky Note8

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

Block 15 - Sticky Note9

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

Block 16 - Sticky Note10

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

Block 17 - Sticky Note11

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

Block 18 - docker compose up

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

Block 19 - Sticky Note12

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

Block 20 - Set Default variable

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

Block 21 - Github HTTP Request

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

Block 22 - Merge Results

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 23 - Edit Version String

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

Block 24 - Comapre Two Input

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

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

3. Summary Table

Workflow Automate docker container updates with Telegram approval system
Complexity advanced
Nodes 27
Categories DevOps
Author Jaber Zare
Published 31 Mar 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3386/3386.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 Automate docker container updates with Telegram approval system do?

Who is this for? This workflow is for DevOps engineers, system administrators, and Docker users who want to automate the process of checking for updates, verifying them, and applying updates to 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 use case.