Skip to main content
Nodes are the steps on a journey canvas. They send messages, branch on data, wait, aggregate events, call external services, and cancel runs. For how a run moves through them at runtime, see . To split traffic across variants and promote a winner, see .

​
Digest and Batch are not the same node

Both hold events back and release them together, and the difference decides which one you want. A Digest releases on a schedule set on the topic, so a reader gets their nine o’clock summary whether two events arrived or twenty. A Batch releases on a condition, either a count or a window, so it fires as soon as enough has accumulated. Reach for Digest when the cadence belongs to the recipient, and Batch when it belongs to the event volume.

​
Every node reads the same run context

A node acts on the data the run already carries: the payload it was invoked with, the profile, and anything a node added earlier. That is why order matters. A node cannot read what a later node produces. A condition that references missing data does not error. It evaluates false, the run takes the other path, and nothing marks it. Check a branch’s decisions against a real run before trusting a path that never fires.