Monitor Unraid server health and send alerts with Telegram
Go to Workflow
Mohamed Ayoub Jabane
Description
Quick overview
This workflow monitors an Unraid server via its GraphQL API, scanning new syslog warnings every minute and running broader health checks every five minutes, then sends deduplicated alerts with suggested next steps to a Telegram chat, with optional Unraid notifications and container auto-restarts.
How it works
Runs on two schedules: every minute for syslog monitoring and every five minutes for health checks.
Calls the Unraid GraphQL API to fetch either only the newly appended syslog lines or a full health snapshot (array, disks, SMART, Docker, notifications, CPU/memory).
Classifies syslog lines and health findings by severity and generates actionable alert details and suggested next steps.
Normalizes alerts and throttles repeats using stored state so the same issue is only sent once per configured time window.
Optionally sends the alert text to a connected chat model for short triage guidance and appends it to the alert.
Sends the formatted alert to Telegram, and optionally mirrors it into Unraid’s notification system and auto-starts stopped autostart Docker containers before reporting the result back to Telegram.
Setup
Create an Unraid admin API key (Unraid Settings → Management Access → API Keys) and configure an HTTP Header Auth credential that sends it as header name x-api-key.
Add a Telegram bot credential and set the target chat ID in cfg.telegramChatId.
Update cfg.unraidUrl to your Unraid WebGUI base URL (HTTPS) and adjust alert options like cfg.minSeverity and cfg.throttleMinutes.
(Optional) Enable cfg.alsoUnraidNotification to create Unraid notifications and/or cfg.autoRestartContainers to auto-start stopped autostart containers.
(Optional) Connect a chat model to the AI triage step and enable it if you want AI-generated guidance included in alerts.
This workflow was created by Mohamed Ayoub Jabane and shared publicly on the n8n community template library. n8nFind indexes it for discovery — the workflow remains the property of its original creator.