Skip to main content
Send nodes deliver a message on one channel (email, SMS, push, etc.). Each links to a journey template that defines the content. A journey can hold multiple send nodes, each with its own channel, conditions, recipient overrides, and delivery timing. In the journeys API, a send node names its channel and template, and can override the recipient under message.to:
Set the send window on the canvas.

Adding a send node

Drag a Send node from the palette onto the canvas, or drop it onto an edge between two nodes. Then choose the channel.

Supported channels

An Order Confirmation journey with the Send Email node selected and its panel showing the Order Received message

Send node configuration panel with an email channel selected and a linked message template

A/B test with an experiment

A send node can run an experiment to A/B test versions of a message. The node holds 2 to 10 variants, each linked to its own journey template. Courier splits traffic across them by weight. Each recipient is assigned one variant deterministically and stays in it across sends. You compare delivery and engagement per variant, then promote one. A send node uses either a single template or an experiment, not both. For traffic allocation, bucketing keys, stickiness, results, and promotion, see Experiments.

Recipient override

By default, a send node delivers to the user who entered the journey, identified by the user_id or profile from the invocation. To send to a different recipient, click Add next to “Recipient Override” in the node’s configuration panel. In the single field that opens, either:
  • Select a field reference from the dropdown. It lists fields from the trigger schema, profile, and upstream fetch node responses. At runtime, that field’s value becomes the recipient address.
  • Type a hardcoded value (e.g., ops@yourcompany.com, +15551234567, or a user ID). Type your value and click away to commit it.
In the API, the override is one field on the node’s message.to, named by channel: Click Remove to revert to the default recipient. Set the destination on every Slack and Microsoft Teams send node, because a journey user has no Slack channel or Teams chat of their own.
The Send Email panel with Recipient Override open on Trigger data fields like data.order_id and data.order_total

Recipient override with the dropdown showing available schema and profile fields

Add a schema field like manager_email to your API trigger, then select it as the recipient override on a send node. Your application then controls who receives that notification without changing the journey.

Slack recipients

A Slack send node needs a destination and an Access Token for the workspace it posts into. Set the destination with Send to:
  • Channel posts to a Slack channel. Enter the channel ID, like C012AB3CD. Courier doesn’t list your channels, so bring the ID from Slack.
  • Direct message goes to one person, addressed by User ID (like U01AB2CD3EF) or Email.
Leave Access Token empty to use the token stored on the recipient’s Slack profile. To post with a different workspace’s token, set it to a reference such as {{data.slack_token}} or a tenant property. Courier rejects a pasted bot token (xoxb-...), so keep the token in your data rather than in the journey. These map onto the fields the Send API uses: For message content, Block Kit layouts, threading, and provider overrides, see the Slack integration.

Microsoft Teams recipients

Set the destination with Send to:
  • Channel posts to a Teams channel. Under Identify channel by, choose Channel ID, or Channel Name plus the Team ID that channel belongs to.
  • Direct message goes to one person. Under Identify user by, choose User ID or Email.
Every destination except Channel ID also needs your Microsoft tenant. Set Microsoft tenant ID, or end the Service URL with the tenant ID, like https://smba.trafficmanager.net/amer/<tenant-id>. With no Service URL, Courier uses https://smba.trafficmanager.net/amer. These map onto the fields the Send API uses: For adaptive cards, thread replies, and provider overrides, see the Microsoft Teams integration.

Conditions

A send node can carry conditions, evaluated at runtime. If they aren’t met, the node is skipped and the journey continues to the next step. Conditions use the same operators and field references as branch nodes. Common patterns:
  • Skip an SMS if profile.phone_number does not exist
  • Only send an email if data.notification_preference equals "email"
  • Send only when a fetch node response indicates the user hasn’t completed an action

Send window

A send window controls when a message is delivered. If the run reaches a send node outside the window, delivery is held until the window opens. Use it to respect business hours, avoid late-night messages, or batch sends into a time range.
Send Windows set to 9:00 AM to 5:00 PM Monday through Friday, no sends on weekends, and the timezone set to the user’s

Send window configuration with per-day time ranges and timezone selection

Enable a send window in the send node’s settings:
  • Day-by-day schedule: Each day of the week has its own row with an opening and closing time (e.g., Mon through Fri, 9:00 AM to 5:00 PM). A day with no time range is blocked entirely.
  • Timezone: Choose User’s timezone (resolved from the recipient’s profile) or UTC. If the recipient has no timezone set, messages are sent in UTC.

Provider resolution

Courier picks the provider from your workspace’s configured integrations. A send node never specifies one. For example, if your workspace has SendGrid configured for email, an email send node routes through SendGrid with no configuration on the node. With multiple providers on the same channel, Courier follows your routing rules.