Build Journeys via UI

Beyond send nodes and triggers, journeys support a set of function nodes that add logic and orchestration to your workflows.

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 Build panel, 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.

An order confirmation journey on the canvas: API trigger, throttle, send, branch on is_first_order, delay, and a welcome guide email on the default path

Node Types

The Build panel groups nodes into channels (one send node per channel you have an integration for) and functions (logic and orchestration).

Channel Nodes

Channel nodes deliver messages on email, SMS, push, inbox, Slack, and Microsoft Teams. Each one targets a single channel and is linked to a journey template. For most channels Courier fills the recipient in from the user who entered the journey. Slack and Microsoft Teams are addressed on the node itself, by channel or by direct message. See Send node 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
AI	Run an LLM prompt to classify, extract, or generate structured data from journey context. The output merges into the context for downstream nodes.	AI reference
Batch	Collect events at a point in the journey and release them together as one aggregated payload, by item count or a wait window.	Batch reference
Add to Digest	Add the event to a subscription topic’s digest, released on the topic’s schedule.	Add to Digest reference
Cancel	Stop in-flight journey runs, either a single run or a group sharing a cancellation token.	Cancel reference

Data Flow

Understanding how data flows through a journey helps you build reliable workflows:

Trigger data: fields from the trigger, meaning your schema fields on an API invocation, the inbound webhook payload, Twilio Segment event properties, or the audience ID. Available everywhere.
Profile data: loaded from the user’s stored profile and any profile overrides in the invocation. Available everywhere.
Tenant data: properties on the tenant, loaded when the invocation carries a tenant_id. Useful for per-customer settings like a channel ID or an access token.
Fetch responses: merged into the journey context using the configured merge strategy. Available in all downstream nodes.
AI output: structured JSON returned by AI nodes, merged into the journey context. Available in all downstream nodes.

Each node can reference data from any upstream source. The journey editor shows available fields in dropdowns and autocomplete, so you can see exactly what data is accessible at each point.

Platform

Developer Tools

Help

Build Journeys via UI

Canvas Basics

Node Types

Channel Nodes

Function Nodes

Data Flow

​Canvas Basics

​Node Types

​Channel Nodes

​Function Nodes

​Data Flow

Canvas Basics

Node Types

Channel Nodes

Function Nodes

Data Flow