Skip to main content
Every send node in a journey is linked to a journey template that defines the notification content. Journey templates are created and edited directly inside the journey editor; they are scoped to the journey where they’re created and are not shared with other journeys or accessible from regular Courier sends.
Journey templates are separate from templates you create in the Courier template designer (the ones used with the Send API). You cannot reference a journey template from a regular send, and you cannot import an existing template into a journey. Each journey manages its own set of templates.

Creating a Template

When you add a send node and select a channel, click + Create to provision a new message template. Courier creates the template, links it to the send node, and opens the template designer in a full-screen overlay.
The template starts as a blank draft titled “Untitled.” You can rename it, add content blocks, and use variables from your journey’s data context.

Editing a Template

To edit an existing template, click Edit in the send node’s configuration panel. The template designer opens in the same full-screen overlay, and any changes are saved to the template’s draft. Templates are versioned alongside the journey. When you publish the journey, the current draft of each linked template becomes the active version.

Using Variables

Templates can reference any data available in the journey context using double-brace syntax: {{variable_name}}. Available variables include:
  • Trigger schema fields defined on the API trigger (e.g., {{order_id}}, {{order_total}})
  • Profile fields from the user’s stored profile or the invocation payload (e.g., {{first_name}}, {{email}})
  • Fetch response fields from upstream fetch data nodes
The template designer shows a list of available fields so you don’t need to remember field names.

Template Lifecycle

StateDescription
DraftCreated when you click ”+ Create.” Editable in the designer. Not yet active.
PublishedBecomes active when you publish the journey. Used for all new invocations.
Templates follow the same publish cycle as the journey itself. Editing a template after publishing creates a new draft; you need to re-publish the journey for changes to take effect. Existing runs in progress continue using the template version that was active when the run started.

What’s Next