AutomationFlowsSlack & Telegram › Server Reboot Telegram Notifications

Server Reboot Telegram Notifications

Original n8n title: Server Reboot Notification

Server Reboot Notification. Uses telegram. Webhook trigger; 5 nodes.

Webhook trigger★★☆☆☆ complexity5 nodesTelegram
Slack & Telegram Trigger: Webhook Nodes: 5 Complexity: ★★☆☆☆ Added:

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 →

Download .json
{
  "name": "Server Reboot Notification",
  "nodes": [
    {
      "parameters": {
        "httpMethod": "POST",
        "path": "server-reboot",
        "responseMode": "responseNode",
        "options": {}
      },
      "id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa",
      "name": "Webhook",
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2,
      "position": [
        240,
        300
      ]
    },
    {
      "parameters": {
        "respondWith": "text",
        "responseBody": "ok"
      },
      "id": "bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb",
      "name": "Respond",
      "type": "n8n-nodes-base.respondToWebhook",
      "typeVersion": 1.1,
      "position": [
        460,
        180
      ]
    },
    {
      "parameters": {
        "conditions": {
          "options": {
            "caseSensitive": true
          },
          "conditions": [
            {
              "id": "cond1",
              "leftValue": "={{ $json.event }}",
              "rightValue": "imminent",
              "operator": {
                "type": "string",
                "operation": "equals"
              }
            }
          ]
        }
      },
      "id": "cccccccc-cccc-cccc-cccc-cccccccccccc",
      "name": "Is Imminent?",
      "type": "n8n-nodes-base.if",
      "typeVersion": 2,
      "position": [
        460,
        420
      ]
    },
    {
      "parameters": {
        "chatId": "={{ $json.chat_id }}",
        "text": "\u26a0\ufe0f <b>Servidor reiniciando</b>\n\nEl servidor se reiniciar\u00e1 en 60 segundos para mantenimiento programado.",
        "additionalFields": {
          "parse_mode": "HTML"
        }
      },
      "id": "dddddddd-dddd-dddd-dddd-dddddddddddd",
      "name": "Telegram Imminent",
      "type": "n8n-nodes-base.telegram",
      "typeVersion": 1.2,
      "position": [
        700,
        300
      ],
      "credentials": {
        "telegramApi": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "chatId": "={{ $json.chat_id }}",
        "text": "\u2705 <b>Servidor reiniciado</b>\n\nEl servidor ha vuelto a estar operativo.",
        "additionalFields": {
          "parse_mode": "HTML"
        }
      },
      "id": "eeeeeeee-eeee-eeee-eeee-eeeeeeeeeeee",
      "name": "Telegram Online",
      "type": "n8n-nodes-base.telegram",
      "typeVersion": 1.2,
      "position": [
        700,
        540
      ],
      "credentials": {
        "telegramApi": {
          "name": "<your credential>"
        }
      }
    }
  ],
  "connections": {
    "Webhook": {
      "main": [
        [
          {
            "node": "Respond",
            "type": "main",
            "index": 0
          },
          {
            "node": "Is Imminent?",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Is Imminent?": {
      "main": [
        [
          {
            "node": "Telegram Imminent",
            "type": "main",
            "index": 0
          }
        ],
        [
          {
            "node": "Telegram Online",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "settings": {
    "executionOrder": "v1"
  },
  "staticData": null,
  "tags": []
}

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.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

Server Reboot Notification. Uses telegram. Webhook trigger; 5 nodes.

Source: https://github.com/ch3rot/server-monitor/blob/724d516cd649aa05b2776ba841c8ad570dc7c9ee/workflows/server-reboot.json — original creator credit. Request a take-down →

More Slack & Telegram workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Proxmox VM Lifecycle Automation. Uses telegram, httpRequest. Webhook trigger; 9 nodes.

Telegram, HTTP Request
Slack & Telegram

This n8n workflow captures Partnerstack events via a webhook, logs the event data into a Google Sheet, and sends a Telegram notification. Webhook Node (Trigger): Listens for incoming POST requests. Wh

Google Sheets, Telegram
Slack & Telegram

Lumen - Contact Form Handler. Uses emailSend, telegram. Webhook trigger; 4 nodes.

Email Send, Telegram
Slack & Telegram

새론금융 SNS 자동화 리드관리. Uses googleSheets, emailSend, telegram. Webhook trigger; 4 nodes.

Google Sheets, Email Send, Telegram
Slack & Telegram

Upload-File. Uses googleDrive, telegram. Webhook trigger; 4 nodes.

Google Drive, Telegram