End Node

The End node marks the intentional stopping point for a workflow branch.

Use End when the workflow has reached the point where that branch should stop cleanly and no further automated action is required.

When to use End

End is appropriate after the workflow has:

It makes branch termination explicit for both runtime behavior and human reviewers.

Execution reaches End from an upstream node.
The current branch stops.
Interaction finalization can later store completion metadata as part of the overall workflow outcome.

End does not send a message or perform an action by itself. It only marks the stopping point.

The main field is the label.

Use it to clarify why a branch ends, especially in larger graphs with multiple success, fallback, or escalation outcomes.

Successful completion Let an AI Agent or Play node respond, then route to End.
Unsupported request Explain the limitation to the user, then terminate that branch.
Post-transfer stop Hand off through Transfer and end the automated path.

The canvas view shows the final stop point for a branch.

Annotated Complete End node on the workflow canvas with its entry port visible

The inspector is minimal because End exists to terminate the branch, not to carry additional logic.

Annotated Complete End node inspector showing the label field

End does not send the final message for you.
Put any final spoken or written response in the previous node.
Every branch should have a deliberate terminal behavior: End, Transfer, Wait, or another intentional continuation path.

Does End send a message? No. Put the final message in an AI Agent or Play node before End.

Does every branch need End? Every branch should have a clear terminal behavior: End, Transfer, Wait, or another intentional continuation path.