⚙️ Monitor TP-Link Omada network disconnections with Gmail & Pushover

325 views · ⚙️ DevOps & CI/CD

Description

Monitor device disconnections from Omada emails to Google Sheets with Pushover alerts

Who’s it for

This workflow is designed for IT admins, network engineers, or small business owners who need to automatically monitor device connectivity from Omada Controller email alerts. If you want a lightweight, low-cost solution for tracking device uptime without complex monitoring software, this template is for you.

How it works

The workflow listens for Omada Controller email alerts using Gmail, parses each email, and logs device connection status (connected/disconnected) into Google Sheets. Every 5 minutes, it checks for devices that have been disconnected for more than 30 minutes. If a device has not reconnected, the workflow sends a push notification via Pushover. Old logs are cleared automatically every 2 days to keep the sheet clean.


Workflow Overview

The workflow is broken into three main parts:

1. Email Processing (Receives Alert -> Append Row in Sheet)

Triggered whenever a new email is received. It uses a Code node to parse the raw text of the email, extracting details like device name, MAC address, and connection status. This data is formatted and appended as a new row to Google Sheets, creating a comprehensive log of all connection events.

Important: In the Gmail trigger node, make sure to set the search field or filter so that it only matches the subject line used by Omada Controller alert emails. This ensures the workflow only processes the intended alerts and not unrelated emails.

2. Disconnected Device Alerting (Check Every 5 minutes -> Alert User)

Runs every 5 minutes. It reads the device log from Google Sheets, identifies the most recent status for each device, and filters for devices currently disconnected. If a device has been disconnected for more than 30 minutes, a high-priority push notification is sent to Pushover account. Once sent, the workflow updates the corresponding row in the Google Sheet to prevent duplicate alerts.

3. Data Maintenance (Clear Rows Every 2 days -> Clear sheet)

Runs every two days to clean up the Google Sheet by deleting the oldest rows, keeping the log from growing too large.


Services and Dependencies

To run this workflow, you’ll need the following services connected to n8n:


Setup Instructions

1. Create a Google Sheet Log

exact spelling and order is crucial rowId, timestamp, timestampISO, category, severity, mac, name, type, status, checkAfter, alertSent, timeStampFormated

2. Configure Credentials

3. Import the Workflow

4. Update the Nodes


Node Breakdown

🔗 Nodes Used

Google Sheets, Pushover, Gmail Trigger, Schedule Trigger

📥 Import

Download workflow.json and import into n8n: Workflow menu → Import from File

📖 Importing guide · 🔑 Credential setup