message.to:
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

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 theuser_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.
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.

Recipient override with the dropdown showing available schema and profile fields
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.
{{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.
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_numberdoes not exist - Only send an email if
data.notification_preferenceequals"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 window configuration with per-day time ranges and timezone selection
- 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.