Termination
Marks a successful stop for a branch. Use the Output tab when you need a final payload shape for invoke responses or downstream consumers.
Overview
The End node tells the runner this branch completed intentionally. Multiple end nodes may exist on a graph when different branches finish separately.
Steps in this family
There is a single termination template today: focus on mapping the fields you want callers or logs to retain.
Configuration
General for naming, and Output to define the final object (often pulling from {{input.*}}, trigger data, or globals). There is no Execution tab.
Data flow
Whatever you map becomes the emitted output for that branch's completion: align keys with whatever your integration expects when a run finishes.