Overview
The "End" node is designed to mark the termination point of a workflow in n8n. It allows users to explicitly indicate where a process should end, and optionally categorize the outcome as "Success", "Fail", or "Warning". This can be useful for visually structuring workflows, signaling completion status, or integrating with other nodes that may react differently based on the type of ending.
Common scenarios:
- Marking the successful completion of a workflow.
- Indicating a failure or warning state at the end of a process.
- Structuring complex workflows with multiple possible endpoints for clarity and maintainability.
Practical example:
A workflow processes incoming data and, depending on validation results, routes to different End nodes labeled as "Success" or "Fail" to clearly communicate the result.
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 an empty object under the key response.
- No binary data is produced by this node.
Dependencies
- No external services, API keys, or special n8n configurations are required.
Troubleshooting
Common issues:
- Since the node does not produce any meaningful data (only an empty response object), downstream nodes expecting specific data may fail or behave unexpectedly.
- If the node is used in the middle of a workflow, subsequent nodes will not execute because the End node has no outputs.
Error messages:
- Errors are unlikely unless misconfigured in the workflow context, such as connecting outputs from the End node to other nodes (which is not supported).