Stop And Error
A core n8n node used to display custom error messages, cause executions to fail under certain conditions and send custom error information to error workflows.
On this page
Source content checked . English translation published 2026-10-27.
In business automation
It has two operations, Error Message (a text) and Error Object (a JSON object). It pairs with the Error Trigger so that business rule failures reach the same alert path as technical failures.
Examples
These examples illustrate a possible workflow. Adapt the connections and rules to your own systems.
A lead without a phone number
Fail the run when a lead arrives without a phone number.
A payment mismatch
Throw an error object with the order id when a payment total does not match.
A missing template name
Stop a WhatsApp send when the template name is missing.
Relevant tools
- n8n
- The definition comes from the official n8n documentation on the Stop And Error node.
What to check
- Placing it where it fails the whole execution by accident. Put it on a branch after an If or Switch check.
- Having no linked error workflow, so the custom message is visible only in the execution log.
- Putting personal data in error objects, since they are copied into alerts.