Database alerts with Notion and SIGNL4
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Function (legacy), Interval. 2 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Function | Code node, mode 'Run Once for All Items' |
| Interval Interval | Schedule Trigger |
Nodes used (6)
- Function
n8n-nodes-base.function - Notion Trigger
n8n-nodes-base.notionTrigger - Webhook
n8n-nodes-base.webhook - Notion
n8n-nodes-base.notion - Interval
n8n-nodes-base.interval - SIGNL4
n8n-nodes-base.signl4
What it does
Objective In industry and production sometimes machine data is available in databases. That might be sensor data like temperature or pressure or just binary information. In this sample flow reads machine data and sends an alert to your SIGNL4 team when the machine is down. When the machine is up again the alert in SIGNL4 will get closed automatically. Setup We simulate the machine data using a Notion table. !image.png(fileId:511) When we un-check the Up box we simulate a machine-down event. In certain intervals n8n checks the database for down items. If such an item has been found an alert is send using SIGNL4 and the item in Notion is updates (in order not to read it again). !workflow-screenshot(fileId:509) Status updates from SIGNL4 (acknowledgement, close, annotation, escalation, etc.) are received via webhook and we update the Notion item accordingly. This is how the alert looks like in the SIGNL4 app. !image.png(fileId:510) The flow can be easily adapted to other database monitoring scenarios.