Monitoring & Alerting Templates
5 workflow templates for monitoring & alerting automation
Meraki Packet Loss and Latency Alerts to Microsoft Teams
This Template gives the ability to monitor all uplinks for your Meraki Dashboard and then alert your team in a method you prefer. This example is a Teams notification to our Dispatch Channel  Setup will probably take around 30 minutes to 1h provided with the Template. Most time intensive steps are getting a Meraki API key which I go over and setting up the Teams node which n8n has good documentation for. Tutorial & explanation https://www.youtube.com/watch?v=JvaN0dNwRNU
Papercut Health Monitoring - Printer Alerts
This workflow monitors the health of printers managed by PaperCut NG/MF and sends a Slack message to a specified channel when any printer reports a status other than "OK". It retrieves printer health information from the PaperCut Health Monitoring API, checks the status of each printer, and generates a message containing details of printers in error.
Database Alerts with Notion and Signl4 - N8n Template
This workflow monitors machine data stored in a Notion table, triggers alerts in SIGNL4 when a machine is down (simulated by unchecking a box in Notion), and automatically closes alerts in SIGNL4 when the machine is back up. It also updates the Notion table with status updates from SIGNL4 (acknowledgement, close, annotation, escalation, etc.) received via webhook.
Send N8n Automation Errors to a Monday.Com Board
This workflow is an error handler that automatically logs errors occurring in n8n workflows to a designated Monday.com board. It captures the error message, stack trace, timestamp, and workflow name, then creates and updates an item on the Monday.com board with this information for troubleshooting and tracking.
Create, Update, and Get a Monitor Using Uptimerobot
This workflow allows you to create, update, and get a monitor using the UptimeRobot node.  **UptimeRobot node:** This node creates a new monitor of the type `HTTP(S)`. **UptimeRobot1 node:** This node will update the monitor that we created in the previous node. **UptimeRobot2 node:** This node will get the information of the monitor that we created in the previous node.