Workflows do not require an End node. When execution reaches a node with no outgoing connections, the workflow completes automatically and returns the last node's output.
Add an End node when you want to explicitly mark completion or configure a final output action.
Configuration
| Field | Description |
|---|---|
| Output action | What to do when the workflow finishes |
Output action types
| Type | Behavior |
|---|---|
| None | Complete silently; last node output is the workflow result |
| HTTP | POST (or other method) a payload to an external URL |
| App | Trigger an app action as the final step |
When to use End
- Clarity — make it obvious where the workflow stops on a busy canvas
- Webhook response — some Start (Webhook) setups benefit from a defined final payload
- Output action — send a completion notification to Slack, log to an API, etc.
When to skip End
- Simple linear workflows (Start → steps → done)
- Loops that exit to a condition branch with no further steps
- Templates where the last Action node is clearly the terminus
Tips
- Multiple branches can each end at their own End node or at a shared one.
- Check Execution Data on the node before End to verify the payload shape your output action will receive.
- Prefer
{{lastOutput}}or specific{{context.nodeId.output}}paths in HTTP/app output configs.