How can I manually trigger an error to activate my Error Workflow using the Stop and Error node?

When you add a Stop and Error node into your workflow, you’re effectively instructing n8n to throw an error—which causes the workflow to fail. Because you have an Error Workflow specified in your workflow’s settings, this failure will automatically trigger that Error Workflow. Here’s how to do it:

1. Add the Stop and Error Node
   Insert the Stop and Error node at the point in your workflow where you want to enforce the error based on your custom conditions.

2. Configure the Error Type
   In the node’s parameters, select one of the two error types:

   • Error Message: Enter a custom error message text.
   • Error Object: Provide a JSON object with additional error details.

   Choose the one that best meets your needs.

3. Execution Flow
   When the Stop and Error node runs, it will throw the defined error. This intentional error will cause the workflow’s execution to fail immediately. Since you’ve set up an Error Workflow in your workflow’s settings, n8n will forward this error—including the message or object details—to that Error Workflow.

By using the Stop and Error node in this way, you can catch run-time conditions and manually cause the workflow to fail so your designated Error Workflow can handle the error (for instance, by sending notifications).

Here’s a simplified JSON snippet of how a Stop and Error node might be set up:

JSONCopied
{
	"nodes": [
		{
			"parameters": {
				"errorType": "Error Message",
				"errorMessage": "Custom error triggered due to condition X"
			},
			"name": "Stop and Error",
			"type": "n8n-nodes-base.stopanderror",
			"typeVersion": 1,
			"position": [
				600,
				300
			]
		}
	]
}

Remember that the Stop and Error node should be placed as the last node in your workflow or in a branch where the error should immediately terminate further execution. When this node triggers the error, your Error Workflow (which must start with an Error Trigger node) will be executed, processing the error payload that includes the generated message.

This approach ensures that you can manually initiate an error condition whenever needed while leveraging the Error Workflow to handle and alert you about issues in your process.