Stop Node
The Stop node ends a subscriber journey at that point. Nothing after it on the same path runs for that subscriber.
What is the Stop node?
Stop is an early exit. Use it when remaining messages should not send, for example the subscriber already converted, should not receive a nurture sequence, or belongs on a branch that must not continue into the shared path after a join.
It is not the same as the End node. End marks the finish of a completed branch. Stop cuts the path short so later nodes on that spine or lane are skipped.
[todo: Screenshot of a Stop node on the workflow canvas between a condition lane and later nodes]
How it works
When a subscriber reaches Stop, execution for that journey ends there. Nodes after Stop on the same path are not processed. On the canvas they appear dimmed so you can see they are unreachable after the stop.
On a Condition or Multi condition lane, Stop only ends that lane. Other lanes still run. The join after the split remains for branches that did not stop. Subscribers who hit Stop do not continue into the shared steps after the join.
[todo: Screenshot of a Stop on one branch with later nodes on that lane dimmed, while the other branch and join remain active]
Configuring the node
Stop has a single required field.
Label
Required. Describe why the journey ends, for example Already converted or Do not continue nurture. The default label is Stop.
There is no delay, tag check, or message on this node. Pair it with a Condition or Multi condition if the exit should depend on subscriber data.
[todo: Screenshot of the Stop side panel with the Label field]
Adding Stop to a workflow
Click the add-node control on an edge, choose Stop, set the label, and save. PushFire inserts it on that connection. Anything that was downstream of that edge now sits after Stop and will not run for subscribers who reach it.
[todo: Screenshot of the add-node menu with Stop selected on a workflow edge]
Common use cases
Exit after a qualifying action
If a tag shows the subscriber already purchased or completed onboarding, route them to Stop so they skip reminder emails.
Quiet a branch that should not rejoin
On a False or Else lane, send nothing further and Stop so those subscribers never enter the shared follow-up after the join.
Best practices
Label the reason. Stop on the canvas does not explain the strategy.
Put Stop after the last useful action on that path. A Stop before a notification means that message never sends.
Do not use Stop as a visual spacer. If the journey should continue, omit Stop or use Wait.
Troubleshooting
If later messages never send, look for a Stop on that path, including on a Condition or Multi condition lane. Dimmed nodes after Stop are skipped on purpose.
If other branches also stop, you placed Stop on the shared spine after the join, not only on one lane. Move it onto the lane that should exit.