Canvas Basics
The journey editor is a visual canvas. Nodes are connected by edges that define execution order. You build a journey by dragging nodes from the palette, dropping them onto edges, and configuring each node in its side panel. Execution flows top-to-bottom. When the trigger fires, the journey evaluates each node in sequence. Branch nodes can split execution into multiple paths; all other nodes have a single output.
Node Types
The palette offers two categories of nodes: channels (send nodes for each configured provider) and functions (logic and orchestration).Channel Nodes
Channel nodes deliver messages. Each one targets a specific channel and is linked to a journey template. See Channels & Send for configuration details.Function Nodes
| Node | What it does | Reference |
|---|---|---|
| Branch | Split the journey into multiple conditional paths. The first path whose conditions are met executes; unmatched runs take the Default path. | Branch reference |
| Delay | Pause execution for a fixed duration or until a specific time. Use it to space out messages or wait for user action. | Delay reference |
| Fetch Data | Make HTTP requests to external services. The response becomes available as variables in downstream nodes. | Fetch Data reference |
| Throttle | Limit how many times a user (or globally) can pass through a point in the journey within a time period. | Throttle reference |
Data Flow
Understanding how data flows through a journey helps you build reliable workflows:- Trigger data — Schema fields from the API invocation or Segment event properties. Available everywhere.
- Profile data — Loaded from the user’s stored profile and any
profileoverrides in the invocation. Available everywhere. - Fetch responses — Merged into the journey context using the configured merge strategy. Available in all downstream nodes.