End

The End node explicitly terminates a flow and returns the conversation to the default responder. It performs no action and has no configuration — it simply marks a deliberate stopping point.

Most flows don't use an End node. When any node has no outgoing connection, the flow terminates automatically. The End node exists to make that termination visible and intentional on the canvas.

When to Use It

Use the End node when you want to distinguish "this flow ends here" from "I forgot to connect something." It documents intent. In flows with multiple branches, explicit End nodes help collaborators understand which paths are complete endings versus paths that should continue elsewhere.

After a goodbye message. When your flow sends a final message and you want to make clear that nothing else should happen.

After handing off to a human agent. The Human Takeover node transfers control, and an End node on that branch signals the bot's job is done.

On error branches where recovery isn't possible. When something fails and the conversation should simply stop.

On the Canvas

The End node has a single input handle and no output handle — nothing can follow it because it's a terminal point. Connect it to whichever node should be the last step in a branch.

What Happens After

When a flow terminates, whether via an End node or an unconnected node, the conversation returns to the channel's default responder. This is the flow configured on the Channel Connector as the idle state — it waits for new messages and can trigger other flows via global keywords.

Nodes That Handle Their Own Routing

Some nodes manage their own branching and won't terminate when left unconnected: Conditional, Formula, Interactive Options, Jump To, Login, Logout, HTTP Request, and Workflow Execute nodes all route based on their results. For these, an explicit End node on branches that should terminate makes the design clearer.