Message

Category: Messaging

Overview

The Message node sends a text reply to the customer and immediately advances to the next node. It supports per-language bodies (English + Arabic) and variable interpolation via {{variable_name}} syntax. Use it for greetings, confirmations, instructions, and any one-way reply where you do not need an answer back.

When to use

Welcome messages and acknowledgements (“Thanks, we received your request”).
Static instructions (“Please share your policy number in your next message”).
Status confirmations after an API call or transfer.
Final closing remarks before a Close node.

Ports

Port	Direction	Description
`in`	input	Receives the flow from the previous node.
`next`	output	Fires immediately after the message is sent. There is no wait for a customer reply.

Configuration

Message body (EN / AR)

The text shown to the customer, with an English and an Arabic field. The English field is required on every Message node; the Arabic field is required when the recipe is set to bilingual. Both fields support {{variable}} interpolation — unresolved variables render as the empty string.

Attachment URL (optional)

Paste a public URL to attach an image, video, audio clip, or document to the message. Leave blank for a text-only message.

Attachment type

When you fill in an attachment URL, pick the media type from the dropdown: image (JPEG / PNG), video (MP4), audio (MP3), or document (PDF). The type controls how the customer’s WhatsApp client renders the attachment.

Common patterns

Acknowledge → Wait → Continue

Message (“One moment, looking that up…”) → API node → Message with the result.

Branched messaging

Use one Condition node to route to different Message nodes based on customer profile or stored variables.

Limits & validation

Plain-text body plus one optional attachment per node. For more elaborate layouts (multiple images, carousels, buttons) reach for the dedicated Card Carousel, Button, or List node.
Soft length cap aligns with WhatsApp text limits; longer bodies are truncated by the channel adapter.

Troubleshooting

{{variable}} appears literally in the customer-facing message.

Confirm the variable was set earlier in the flow (Set Variable node) or comes from a Question. Unresolved variables render as the empty string by default — verify spelling.

Arabic body never shows.

Customer language is detected from the contact profile; if your test account has no language preference set, the recipe falls back to English.