Overview
The "End" node is designed to mark the logical end of a workflow branch in n8n. It allows users to explicitly indicate that no further processing should occur after this point for a given execution path. This can be useful for visually structuring workflows, handling conditional branches (e.g., success, failure, warning), or simply improving workflow readability.
Practical examples:
- Use the End node after an error-handling branch to stop further execution.
- Place it at the end of a successful process to clearly indicate completion.
- Use different "Type" options to document the outcome of each branch (Success, Fail, Warning).
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | options | Specifies the type of end state: Success, Fail, or Warning. Used for documentation only. |
Output
The node outputs a single item with the following structure:
{
"response": {}
}
- The output contains a json field with an empty response object.
- No binary data is produced.
Dependencies
- No external services, API keys, or special n8n configurations are required.
Troubleshooting
- No Output Data: The node always outputs an empty object; this is by design. If you expect data from this node, review your workflow logic.
- Node Not Stopping Execution: The End node does not forcibly terminate the entire workflow; it only marks the end of its own branch. Other branches may continue running as per n8n's workflow engine.