Check broken error workflows via the n8n API and Telegram alerts

Ready for 3.0

by Benzy · 1 views · created 2026-09-24 · DevOps

Ready 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 7 nodes and runs on a schedule (every day at 08:00). Along the way it connects Telegram.

How it runs

Trigger: On a schedule (every day at 08:00).

Settings (Edit Fields (Set)): sets 2 fields: telegramChatId, alertWhenClean
Get workflows (n8n): get many (workflow)
Check error routing (Code): runs custom JavaScript code
Anything to report? (If): checks a condition and branches into true / false
Send to Telegram (Telegram): uses Telegram

Services it uses

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 Triggern8n-nodes-base.scheduleTrigger
Edit Fields (Set)n8n-nodes-base.set
n8nn8n-nodes-base.n8n
Coden8n-nodes-base.code
Ifn8n-nodes-base.if
Telegramn8n-nodes-base.telegram
No Operation, do nothingn8n-nodes-base.noOp

From the author

Quick overview This workflow runs daily, reads your n8n instance via the n8n API, checks every workflow’s configured error workflow handler for common silent failures, and sends a grouped status report to Telegram when issues are found (or always, if…
Excerpt from Benzy's description on n8n.io.

View the original on n8n.io → Check your own copy

Check broken error workflows via the n8n API and Telegram alerts

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (7)

From the author

Get the weekly “what broke” email