Detect smart meter anomalies and route critical alerts via HTTP API
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 13 nodes and runs on a schedule (cron 0 * * * *) (plus 1 other trigger). It uses only n8n's built-in nodes.
How it runs
Trigger: On a schedule (cron 0 * * * *) (plus 1 other trigger).
- Set Configuration Parameters (Edit Fields (Set)): sets 10 fields: meterApiUrl, meterGroupId, lookbackHours…
- Fetch Smart Meter Readings (HTTP Request): calls an HTTP API
- Wait: pauses before continuing
- Analyze Consumption Patterns (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Classify Anomaly & Build Alert Payload (Code): runs custom JavaScript code
- No Anomaly - No Action (Edit Fields (Set)): sets 1 field: note
- If: checks a condition and branches into true / false
- Wait: pauses before continuing
- Prepare Standard Alert Log (Edit Fields (Set)): sets 2 fields: dispatchChannel, readyForDispatch
…plus 1 more step. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - Code
n8n-nodes-base.code - If
n8n-nodes-base.if
From the author
Quick overview This workflow runs hourly (or manually) to pull recent smart meter readings from a metering API, detect abnormal consumption patterns (spikes, drops, leakage, and stuck meters), and prepare either a critical escalation payload or a standard log…