Monitor n8n workflows with Watchflow dead man’s switch and error alerts
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs when another workflow fails (error workflow) (plus 1 other trigger). Along the way it connects Watchflow (community).
How it runs
Trigger: When another workflow fails (error workflow) (plus 1 other trigger).
- Mark job as failed (Watchflow): fail
- Get Items (Edit Fields (Set)): sets 1 field: data
- Split Out: splits a list into separate items
- Set Label (Edit Fields (Set)): sets 1 field: label
- Aggregate: combines items into one
- If: checks a condition and branches into true / false
- Mark job as successful (Watchflow): uses Watchflow
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @watchflow/n8n-nodes-watchflow is verified or supports 3.0 (used in Mark job as successful, Mark job as failed).
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Watchflow
@watchflow/n8n-nodes-watchflow.watchflow - No Operation, do nothing
n8n-nodes-base.noOp - Error Trigger
n8n-nodes-base.errorTrigger - Edit Fields (Set)
n8n-nodes-base.set - Split Out
n8n-nodes-base.splitOut - If
n8n-nodes-base.if - Aggregate
n8n-nodes-base.aggregate
From the author
🚀 Your n8n Workflows Monitoring Best Practices Template Are you running critical processes in n8n and relying on hope that they finish successfully? Stop guessing and start monitoring. This template demonstrates best practices for monitoring your n8n…