This workflow follows the HTTP Request → Telegram recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
sshPasswordtelegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
n8n update. Uses ssh, httpRequest, telegram. Event-driven trigger; 27 nodes.
Source: https://github.com/fsebbah/n8n-workflows/blob/cfce483f81a240422fd048e1c680c746b877429a/workflows/n8n_update.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
n8n update. Uses ssh, manualTrigger, scheduleTrigger, stickyNote. Event-driven trigger; 27 nodes.
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 depl
Docker. Uses ssh, httpRequest, telegram. Event-driven trigger; 27 nodes.
🚀 Say Goodbye to Manual Rule Deployments in Wazuh!
N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.