💬 Message Node¶

Purpose¶

The Message node sends a text message to the customer. It's the most basic and frequently used node — perfect for greetings, informational responses, confirmations, and any text you want to deliver.

Business Scenario¶

Use the Message node when you need to:

Greet customers with a welcome message
Provide information like business hours, addresses, or policies
Confirm actions such as "We've received your details!"
Guide customers with instructions before a menu or question
Include saved data using variables like {{name}} or {{email}}

Configuration¶

Field	Description
Title	Internal name for the node (only visible to you in the designer)
Message Body	The text content sent to the customer on WhatsApp. Supports `{{variable}}` placeholders.

WhatsApp Character Limit

Message bodies are limited to 1,024 characters. The Inspector shows a live counter (e.g., 142/1024) and highlights in red when you exceed the limit.

Properties¶

Property	Type	Required	Default	Description
`title`	Text	No	`""`	Internal node name
`body`	Text	Yes	`""`	The message content sent to the customer

Inputs¶

Handle	Type	Description
Top (↑)	Target	Receives a connection from any preceding node

Outputs¶

Handle	Type	Description
Bottom (↓)	Continue	Connects to the next node in the flow

Connection Rules¶

✅ Can receive connections from any node type
✅ Can connect to any node type
⚠️ If there is no outgoing connection, the conversation stops here (dead end — the designer will show a warning)

Example Flow Diagram¶

flowchart TD
    A["🚀 Entry Point"] --> B["💬 Welcome Message<br/><em>Hi {{name}}! Welcome back.</em>"]
    B --> C["📋 Main Menu<br/><em>How can I help?</em>"]
    C -->|"About Us"| D["💬 About Us<br/><em>We're a tech company...</em>"]
    D --> C

    style A fill:#dcfce7,stroke:#22c55e,stroke-width:2px
    style B fill:#dbeafe,stroke:#60a5fa,stroke-width:2px
    style C fill:#ede9fe,stroke:#8b5cf6,stroke-width:2px
    style D fill:#dbeafe,stroke:#60a5fa,stroke-width:2px

Using Variables in Messages¶

You can insert previously captured data by wrapping variable names in double curly braces:

Syntax	Replaced With
`{{name}}`	The customer's name (captured by a Question node)
`{{email}}`	The customer's email
`{{selected_service}}`	A value the customer chose from a menu or question

Example message body:

Thanks, {{name}}! We've noted your interest in {{selected_service}}.
Our team will reach out to {{email}} within 24 hours.

Best Practices¶

Keep messages concise — customers on WhatsApp expect short, clear messages. Aim for 2–3 short paragraphs.
Use emoji sparingly — they add personality but too many look unprofessional.
Name your nodes descriptively — use titles like "Welcome Message", "About Us Response", "Booking Confirmation" so your flow is easy to read.
Add a "back to menu" hint in informational messages (e.g., "Type 'menu' to see options.").
Use variables to personalise messages — Hi {{name}}! is much warmer than Hi!.

Common Mistakes¶

Mistake	What Happens	Fix
Empty message body	Warning: "Node has no content"	Add text to the Message Body field
Exceeding 1,024 characters	Message may be truncated on WhatsApp	Shorten the text or split into multiple Message nodes
Message is a dead end	Warning: "Node is a dead end"	Connect it to the next step (or loop back to a Menu)
Unescaped `{{variable}}` that doesn't exist	The raw `{{variable}}` text appears to the customer	Make sure the variable was captured by a Question node earlier in the flow

🚀 Entry Point — Typically connects into the first Message node
📋 Menu — Often placed after a Message to give customers choices
📥 Question — Captures input that can be used in Message variables
📄 Document — Send a file alongside or instead of a text message
🖼️ Image — Send an image alongside or instead of a text message