UptimeRobot Alert Notifications to Telegram with Visual Verification - n8n Workflow

DevOps Engineers: Needing fast, actionable alerts about service outages. Site Reliability Engineers (SREs): Seeking visual verification (screenshots) alongside downtime notifications. Technical Teams: Who rely on Telegram for critical system notifications. n8n Automation Specialists: Looking for advanced n8n workflow examples combining email parsing, API calls, binary data handling, and conditional routing.

Monitoring mission-critical services requires immediate and detailed alerting. Relying solely on standard UptimeRobot emails can sometimes lack the context needed for rapid response. This sophisticated n8n workflow solves this by transforming a simple email alert into a rich, actionable notification delivered directly to Telegram.

This specific n8n template starts with the email, uses custom JavaScript in an n8n node to extract the Monitor ID, queries the UptimeRobot API for comprehensive logs and details, and crucially, offers an optional visual verification step. If enabled, the n8n workflow captures a live screenshot of the down service using the ScreenshotMachine API, embedding this binary data directly into the Telegram message. This high-value automation ensures you get full context—text status updates and visual proof—immediately when an incident occurs, making this n8n automation highly efficient for monitoring operations.

This comprehensive n8n workflow executes a detailed sequence of steps to process the alert:

1. Trigger and Filtering: The process begins with the Gmail Trigger n8n node, constantly monitoring a mailbox for new emails sent specifically from [email protected].


2. Configuration Check: The flow immediately passes the data through the Conf n8n node, which defines global settings, including whether to takescreenshot (a core feature of this n8n workflow).


3. Initial Parsing: The Extract ID and URL n8n node utilizes custom code (JavaScript) to parse the raw email text using a regex pattern. This extracts the Monitor Dashboard URL and the unique 9-digit Monitor ID, which are essential for the next API call.


4. Data Enrichment: An UptimeRobot n8n node then uses the extracted Monitor ID to call the UptimeRobot API, retrieving the full status, logs, friendly name, and last status change details for that specific monitor.


5. Status Mapping: The Extract Status Details n8n node processes the API output, mapping numerical status codes (e.g., 2, 8, 9) into clear, readable labels (e.g., "up", "down").


6. Conditional Routing: The If Screenshot Required n8n node checks the takescreenshot setting from the Conf node.

1. Telegram Delivery: If a screenshot was taken, the Send a photo message n8n node sends the image and a detailed caption (using enriched data) to the target Telegram chat. In all cases (successful screenshot or conditional bypass), the Send a text message n8n node delivers a standardized, detailed status update, ensuring the team receives all critical information promptly. This robust n8n workflow ensures reliable communication.

To deploy this powerful n8n workflow template, follow these steps:

1. Import: Copy the entire JSON code provided and paste it into a new n8n workflow.


2. Gmail Trigger Setup: Configure the Gmail Trigger n8n node with credentials for the Gmail account receiving UptimeRobot alerts. Ensure the poll times and sender filter are correct.


3. UptimeRobot Credentials: Set up credentials for the Get many monitors n8n node using your UptimeRobot API key (ensure it has Monitor Read permissions).


4. Telegram Credentials: Set up credentials for the Telegram n8n node (Bot Token). Replace the placeholder your-chat-id-goes-here in both Telegram n8n nodes with your actual target Chat ID.


5. Configuration Node (Conf): In this n8n node, set takescreenshot to true if desired. Update the screenshotmachinesecret with your key.


6. ScreenshotMachine Credentials (Optional): If using the screenshot feature, configure the HTTP Request n8n node with Query Auth credentials containing your Customer Key from ScreenshotMachine.


7. Activation: Save and activate the n8n workflow.

Gmail Trigger: This crucial n8n trigger listens for new emails from UptimeRobot ([email protected]), initiating the entire automation when an alert is detected.
Conf (Set node): Acts as a central control panel for this n8n workflow, defining boolean parameters like takescreenshot and configuration settings for the screenshot API (e.g., dimension, device).
Extract ID and URL (Code n8n node): Executes custom JavaScript and regex to precisely parse the monitor's URL and unique ID from the incoming email body, overcoming the limitations of standard email parsing.
Get many monitors (UptimeRobot n8n node): Fetches the full, raw monitoring details, logs, and metadata using the extracted Monitor ID, providing the necessary context that the original email lacked.
Extract Status Details (Code n8n node): Maps the raw numerical status codes received from the UptimeRobot API into human-readable strings (e.g., 'down', 'up'), significantly improving the clarity of the final notification.
If Screenshot Required (If n8n node): Provides conditional flow control based on the takescreenshot variable, determining whether the subsequent, resource-intensive screenshot steps are executed.
Screenshotmachine-secret (Crypto n8n node): Calculates a mandatory hash signature required for secure authentication when requesting the website screenshot, ensuring the HTTP Request n8n node functions correctly.
HTTP Request: Sends the request to ScreenshotMachine to capture the current state of the down website, returning the result as binary data.
Send a photo message (Telegram n8n node): If a screenshot is captured, this n8n node sends the visual binary data along with a rich, detailed caption containing all monitor status information.
Send a text message (Telegram n8n node): Ensures that a detailed text notification is always delivered to Telegram, regardless of whether the screenshot was taken or failed.