Exit Flow node reference
You can stop a visitor's current flow with Exit Flow. See where to place it, why an empty branch behaves differently, and what happens to earlier actions.
Exit Flow ends the current flow and dismisses the widget running it. Use it when a visitor shouldn't see any more questions, forms, or offers on that path.
When to use it
Put Exit Flow after a condition or router when you want some visitors to leave the flow while others continue.
For example, WorkForge (opens in a new tab) could check whether the visitor is on a page that shouldn't show a survey. The Yes path gets Exit Flow, and the No path gets the survey. Put that condition before any action that shouldn't run on the excluded page.
If you want a visible confirmation after a form, use a Submit Message instead. If you want to send visitors to another page, use a Redirect. Exit Flow only ends the current flow.
Settings
You'll find Exit Flow in the Flow group under Build. It has no configurable editor fields, including no URL, message, delay, or audience setting. The condition or router before it decides who reaches it.
The widget's After it's dismissed settings control how long it stays dismissed. On a future visit, the widget can evaluate the flow again according to its rules and remembered visitor data.
How visitors move through it
When a visitor reaches Exit Flow, later steps on that path don't run. The canvas dims unreachable nodes after a step that ends the path and prevents you from inserting nodes into those disabled areas.
Why an empty branch is different
An empty Condition or Router branch can rejoin the shared steps below the decision. Exit Flow stops the path before those steps.
Suppose both paths of a page condition rejoin before a signup form. Leaving the excluded-page path empty still lets that visitor reach the form. Adding Exit Flow to that path prevents the form from appearing.
Things to know
An exit doesn't undo earlier actions. Variables, score adjustments, and webhooks that ran before it stay as they were.
It also doesn't delete the flow, disable every attached widget, remove stored answers, or clear dismissal settings. Another eligible widget can run its own flow.
Check both paths when testing. The excluded visitor shouldn't reach any later question, form, or data action. The allowed visitor should continue. Use the debugger to check which path ran rather than relying on a blank widget, and make sure the exit isn't on a shared path that stops both visitors.
Stopping a system flow
A system flow doesn't need to display anything to finish. You can leave a nonmatching branch empty when no action should run.
To stop a published system flow entirely, change System Flow and publish. Disabling a widget won't stop a flow that runs without one. See pause a flow or widget for the steps.
For other ways to end a path, see flow nodes and execution rules. Condition covers the audience checks you can put before an exit.