25 Payments Marked Failed While n8n Said Success: Now a Daily Health Check Emails Only When a Workflow Is Quietly Broken
- Level Intermediate
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What did they do with n8n?
An n8n admin found a sub-workflow left unpublished for five hours had failed 25 payment records while the parent reported success, and a weekly job had failed for three weeks unnoticed. He built a daily n8n workflow that uses the n8n API (read-only) to catch failed runs, missed schedules, broken error paths and calls to unpublished workflows, and emails only when something's wrong. He shared it as a free template.
How it went
n8n community post by nikoada (Nov 10, 2026 UTC): unpublished sub-workflow failed 25 payment records while the parent showed success; a weekly workflow failed 3 weeks unnoticed; over a third of live workflows had no working failure path; free template in the n8n library. Notes it can't catch jobs that ran on stale data. A health check can't tell if data was stale or wrong; that still needs someone who knows what each workflow should produce
Worth knowing
- n8n community post by nikoada (Nov 10, 2026 UTC): unpublished sub-workflow failed 25 payment records while the parent showed success; a weekly workflow failed 3 weeks unnoticed; over a third of live workflows had no working failure path; free template in the n8n library. Notes it can't catch jobs that ran on stale data.
- A health check can't tell if data was stale or wrong; that still needs someone who knows what each workflow should produce.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Build an n8n workflow that runs every morning, uses the n8n API read-only, and checks: failed executions in the last 24 hours, schedules that should have run and didn't, workflows with no working error path, and Execute Workflow calls that point to unpublished workflows. Email me only when something is wrong, plus an optional weekly all-clear.
Recommended
Try it in Grok Bot
Grok Bot can do this too: connect the n8n API and ask for the same daily read-only check as a routine.
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (Email) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in n8n, Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: Email · Stack: n8n
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
n8n community post by nikoada (Nov 10, 2026 UTC): unpublished sub-workflow failed 25 payment records while the parent showed success; a weekly workflow failed 3 weeks unnoticed; over a third of live workflows had no working failure path; free template in the n8n library. Notes it can't catch jobs that ran on stale data. A health check can't tell if data was stale or wrong; that still needs someone who knows what each workflow should produce (as of 2026-11-10)
Source: Web · 2026-11-10 · Verified by us: not yet · Report broken or outdated