Skip to Content
GuidesJourneysSend node

Send node

The send node (type: send) delivers a message to the contact through a configured channel. The channel named on the node is the preferred channel — the final channel is resolved by journey-driven dispatch (chat-first, warm-offer collapse, fallback ladder, frequency caps, cross-campaign suppression).

Configuration

Channel selection

Pick one channel per send node:

  • WhatsApp — select an approved template with variable substitution
  • Email — pick a template or use the inline editor
  • SMS — enter text with character count and DLT template selection (India)
  • RCS — select a rich message template
  • Push — title, body, image, and deep link
  • In-App — modal, banner, or survey via the visual editor

To send via multiple channels in the same journey, add multiple send nodes in sequence or in parallel branches. Each send node handles one channel.

Template variables

Templates support dynamic variables pulled from the contact’s profile or the triggering event:

Hi {{contact.first_name}}, your order {{event.order_id}} has shipped!

Available variable sources:

  • contact.* — any contact property (name, email, plan, custom fields)
  • event.* — properties from the triggering event
  • journey.* — journey-level variables (e.g., a coupon code generated at entry)

Priority and fallback

If the contact isn’t reachable on the selected channel (e.g., no phone number for WhatsApp), the send node can:

  • Skip — move to the next node without sending (default)
  • Fallback — attempt delivery on an alternate channel (configurable per node)

Quiet hours

Respect contact timezone and quiet hours:

  • Enable quiet hours — don’t deliver between 9 PM and 8 AM in the contact’s timezone
  • If the send lands during quiet hours, it’s held and delivered when the window opens

Behavior after send

The send node completes immediately after the message is queued (not after delivery). Delivery happens asynchronously. If you need to branch based on whether the message was opened or clicked, add a wait node after the send with an event wait on email_opened or whatsapp_read.

What’s next

Wait nodeBranch node