Creating a unified Error handling without calling another workflow

There is a setup to trigger “Error Workflow” but is it possible to have a “workflow level” error handling? Meaning i could have multiple node blocks, but i could trigger the error notification (highlighted in red below) so it looks more dedicated for error handling?

Information on your n8n setup

  • n8n version: 1.25.1
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker, Localhost
  • Operating system: Win11Pro

Why you need to do so?

Dedicated error workflow is simpler because you only need to set it inside the desired workflow to get error emails. Doing so inside the desired workflow is pointless as there is no option to fix it during the error state.

You can, however, enable the error output inside each node you want to handle errors for.

i evaluated the node’s “On Error” > Continue (using error output) branch out for the error node. It doesn’t look scaleable.

Reason why i dont use a dedicated error workflow due to each workflow counted in license, and in Pro only 15 available workflow allowed.

@weilies_chok Create a new error workflow. Most of these error workflows are reusable since they receive the same error. Once you have a new error workflow, just set it as the error workflow.

Your current method means you build a new error workflow for each process you automate

@barn4k This is useful when you wan to process the specific error in that node in a different method. This does not however call the error workflow