Overview
The "End" node is designed to mark the conclusion of a workflow or a logical branch within an n8n automation. It does not perform any data processing or transformation but serves as a clear endpoint indicator. This can be useful for visually structuring workflows, signaling successful completion, failure, or warning states, and improving workflow readability.
Practical examples:
- Use the End node after a series of conditional branches to clearly indicate where each path terminates.
- Mark the end of a process that should not output data to subsequent nodes.
- Signal different outcomes (success, fail, warning) at the end of a workflow for documentation or monitoring purposes.
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | options | Specifies the type of end state: "Success", "Fail", or "Warning". Default is "Success". |
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 by this node.
Dependencies
- No external services, API keys, or special n8n configurations are required.
Troubleshooting
- No Output Data: The node intentionally outputs only an empty object. This is expected behavior; it does not pass through or transform input data.
- Downstream Nodes Not Triggered: Since the node has no outputs defined, it will not trigger any downstream nodes. Ensure this matches your intended workflow design.