If you’re only relying on n8n’s built-in error messages, I can definitely see the frustration. They may be technically correct, but they don’t always tell you what to do next.
A few tutorials from my recent n8n QA/testing series here in the community may help if you want to build your own stronger error-handling system:
Article 7: Using execution logs to find the failed node, inspect input/output data, and trace the real cause.
Article 4: validating data early so missing fields get caught before nodes like HTTP Request fail.
Article 6: Setting up an error workflow so failures get logged and alerted in a more useful way.
Your Chrome extension idea could be valuable, especially if it combines the error message with execution-log context instead of only explaining the generic error text.