Error Check Node

Overview

The Error Check Node inspects the input data for error messages from previous nodes in a workflow. It helps control the workflow execution by detecting errors and deciding whether to stop or continue based on user configuration. This node is useful in scenarios where you want to handle errors explicitly, such as alerting users, logging errors for developers, or managing backend error flows.

For example, if a preceding node fails to fetch data from an API, this node can detect that error and either halt the workflow or allow it to proceed while capturing the error details for later review.

Properties

Output

The node outputs two arrays:

1. First output: An array of items without errors (successful data).
2. Second output: An array of error objects with the following structure in their json field:

   {
     "message": "Error detected in node: <Node Name>",
     "errorType": "<Error Message Target value>",
     "details": "<Error message string>"
   }
   

This allows downstream nodes to process successful results separately from errors.

The node does not output binary data.

Dependencies

• No external services or APIs are required.
• Requires standard n8n environment with access to workflow input data.
• Uses n8n's built-in error handling utilities.

Troubleshooting

• Common issue: If the node throws an error stopping the workflow unexpectedly, check the "On Error" property; setting it to "Continue Workflow" will prevent halting.
• Error message: "Workflow stopped due to error: <error details>" indicates an error was detected and the node was configured to stop execution. To resolve, either fix the source error or change the "On Error" setting.
• Ensure that previous nodes properly set error information in their output JSON under the error key for this node to detect it.

Links and References

• n8n Documentation - Creating Custom Nodes
• n8n Workflow Error Handling Concepts