Building an error monitoring tool for n8n - would you use it?

Questions
1

Hey everyone,

I’ve been using n8n in production for a while now, and one thing keeps bugging me: error handling sucks.

Don’t get me wrong - n8n is amazing. But when workflows fail:

  • Errors are scattered across different workflows

  • No central place to see what’s broken

  • Debugging takes forever (“which node failed? what was the input?”)

  • I’ve definitely lost hours (and money) because a workflow failed silently

I know you can set up Error Trigger → Slack/Email, but it’s:

  • Per-workflow setup (tedious)

  • Just a notification, no analysis

  • No history, no patterns, no insights

So I’m thinking of building a simple tool:

  • One dashboard showing ALL your n8n errors

  • See which node failed, what data it received, full stack trace

  • AI analysis: “This looks like an API auth error. Check if your HubSpot token expired.”

  • Email/Slack alerts when something breaks

  • Error trends (is this workflow getting worse?)

Setup would be simple: import our template workflow, add your API key, connect it as Error Workflow to your flows. Done.

My questions for you:

  1. Would you actually use this? Be honest - I don’t want to build something nobody needs.

  2. What’s the #1 thing you’d want? Central dashboard? AI suggestions? Something else?

  3. Would you pay for it? Thinking ~€15-20/month for unlimited errors. Or should it be free with limits?

  4. What’s your current workaround? Curious how you handle errors today.

I’m not trying to sell anything - this doesn’t exist yet. Just validating if it’s worth building.

Thanks!

2

Hi @Francesco_Marzano ,

Personally, no I would not use something like this especially if I have to pay for something I have already built.

It was simple enough to build an error workflow which currently stores all errors into a supabase error table, send a telegram to the support group as well as an email to a support group.

Although the notifications does not contain analysis, we’re already technical enough to dissect errors and create fixes based on whether it was network related or bad data vs a repeating bug.

Your argument on error flows being per workflow is not correct as it’s simple enough to have a central error workflow pointed to by any workflow on the same instance.

Since we now have history data in the errors table we could do analysis but that wont be useful to me. It’s more important for me to be made aware there was an error or and ongoing issue over what the reason was for an error.

How do you plan on building this? If it is a template workflow people need to import, then how will you control a per month charge once they have ownership of the workflow?

Maybe this is useful for non-technical people building workflows, but for me personally the answer is no

3

Yes, I think error handling in n8n would be great, I know that there are nodes that do something in the field of error handling but something more involved would be great.

I think that a Dashboard and AI suggestions would be good, though I really think AI suggestions would be the best or at least any information regarding what the actual error is and diagnostic tools for trying to fix it.

I think a free tool atleast at first would be a good way for users to see the opportunities there can be with this error monitor.

Currently we just look at the error logs for information regarding any errors we find in n8n and it can be a challenge because things can fail or just not work without us really knowing why or even getting an error which is tough. I would love to see someone try to solve those issues with errors.