Overview
The "End" node is designed to mark the logical end of a workflow branch in n8n. It allows users to explicitly indicate where a process should terminate, and optionally specify the outcome type (Success, Fail, or Warning). This can be useful for organizing complex workflows, improving readability, and controlling execution flow based on different end states.
Practical examples:
- Marking successful completion of a data processing pipeline.
- Indicating a failed validation step and stopping further execution.
- Signaling a warning state when certain conditions are met, without treating it as a hard failure.
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | options | Specifies the outcome type for the end node. Options: Success, Fail, Warning. |
Output
The node outputs a single item with the following structure:
{
"response": {}
}
- The output contains an empty object under the key response. No additional data is provided by this node.
Dependencies
- No external services, API keys, or special n8n configurations are required.
Troubleshooting
- No Output Data: Since the node always outputs an empty response object, users expecting data from this node will not receive any. This is by design.
- Misplaced End Node: Placing the End node too early in a workflow may prevent subsequent nodes from executing.
- Type Property Ignored: The selected "Type" (Success, Fail, Warning) does not affect the output structure; it's primarily for organizational or visual purposes.