End
Marks a workflow run as finished.
When a run reaches an End node, that path of the workflow is complete. Every workflow needs at least one End node.
When to use it
Place an End node at the finish of each path your workflow can take. Because Logic & Control Flow nodes can split a run down several paths, it's normal to have more than one End node — one at the end of each branch.
Inputs & outputs
| Input handle | One. Connect the last node of a path into it. |
| Output handle | None — nothing runs after End. |
Parameters
The End node has no parameters to configure.
Example
A workflow that checks a condition and finishes differently on each path uses two End nodes:
┌─ (true) → [ Connection: NetSuite ] → [ End ]
[ Start ] → [ Conditional ]
└─ (false) → [ Message: skipped ] → [ End ]
Both paths terminate cleanly at their own End node.
tip
A path that never reaches an End node will look "unfinished." If a run seems to hang on a branch, check that every path leads to an End node.