Keep your n8n Docker server current with a safe, chat based update flow. Teams that run self hosted n8n can use this to check for new releases and upgrade with one tap approval in Telegram.

A schedule runs every three days or you can start it by hand. Default variables store your server folder, container name, and Telegram chat id. The flow pulls the latest release tag from GitHub, removes extra text from the tag, and reads the installed version from Docker over SSH. Results are merged and compared. If versions match, a Telegram note confirms no action. If a newer build exists, Telegram asks for approval. On approval, the server pulls the new image, runs docker compose pull and up in the right folder, and then sends a success message in Telegram.

You need SSH access to the host, Docker installed, and a Telegram bot with your chat id. Expect checks to run on time and updates to finish in minutes, which saves hands on work and lowers risk. This works well for IT teams, small agencies, and admins who manage one or many n8n instances. Follow the steps below to set credentials, fill the default variables, and test the path end to end.

• Schedule trigger runs checks every three days at a set hour
• Manual trigger lets you test or run updates on demand
• HTTP request pulls the latest release tag from GitHub
• String edit removes extra text like n8n at from the tag
• SSH command reads the current container image version
• Merge node combines installed and latest versions for compare
• Decision step sends Telegram no action message if up to date
• Approval in Telegram starts image pull and compose up over SSH
• Final Telegram message confirms update completion

• Reduce manual release checks from 30 minutes to 3 minutes
• Automate about 90 percent of update steps with human approval
• Lower production risk by gating updates through Telegram
• Connect GitHub, your server, and Telegram in one flow
• Run the same update method across many servers with one template

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Telegram, GitHub and SSH. See the Tools Required section above for links to create accounts with these services.
3. Create a Telegram bot with BotFather and copy the bot token. Send a message to the bot to start the chat and note your chat id. You can use a chat id bot to get it.
4. In n8n, open Credentials and create a Telegram credential. Choose Telegram API, paste your bot token, and save. Use a clear name like Telegram Bot Prod.
5. In Credentials, create an SSH Password or SSH Key credential for your server. Enter host, port, username, and password or key. Test the connection if available.
6. If the GitHub request hits rate limits, create a GitHub personal access token and add it in the HTTP Request node header as Authorization with token value.
7. Open the Set Default variable node. Fill working directory with the folder that contains your docker compose file. Set the container name that runs n8n. Add your Telegram chat id.
8. Check the Schedule Trigger settings. It is set to run every three days at a set hour. Adjust if your team needs a different time.
9. Confirm the SSH nodes use your SSH credential. Double click each SSH node and pick your SSH credential from the dropdown.
10. Confirm the Telegram nodes use your Telegram credential and the chat id field pulls from the Set node if mapped.
11. Click Test workflow to run once. If your versions match, you should get a Telegram message that no update is needed.
12. To test the update path safely, try on a staging server first. Approve the update in Telegram and watch the logs for pull, compose pull, and compose up.
13. Troubleshoot tips: if SSH fails, check host and user. If compose commands fail, verify the working directory path. If Telegram is silent, confirm the chat id and bot token.