Send WhatsApp messages with templates, buttons, and optional wait-for-reply.
The WhatsApp action sends an outbound message to the customer. It supports simple custom content, approved templates, interactive buttons, and optional wait for user response (which creates timeout sub-nodes on the canvas).
When to use
- Proactive outbound messages in a flow (not only replies).
- Template-based notifications (marketing/utility templates).
- Collecting a reply before continuing — enable Wait for user response.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Message Type | custom (simple) or template (WhatsApp-approved template). | Use template when Meta requires a pre-approved template; use custom for free-form session messages where allowed. |
| Template (template mode) | Pick and fill an approved template; header/body/footer may be read-only for catalog templates. | Order updates, OTP, structured notifications. |
| Header | Optional media or text header. | Templates or rich messages with a title line. |
| Body | Main message text; supports variables from upstream nodes. | Always — core message content. |
| Wait for user response | Pauses the flow until the user replies; adds timeout handling on the canvas. | Surveys, confirmations, menu choices before the next step. |
| Buttons | Quick-reply or call-to-action buttons (when not read-only). | Short menus; limited options instead of free text. |
| Footer | Small print under the message. | Disclaimers, unsubscribe hints. |
| Description | Optional canvas note at the bottom of the node when filled in | Team documentation — see Node descriptions |
Message Type
- Simple (
custom) — edit header, body, footer, and buttons directly. - Template — select a template from your WhatsApp Business account; fields may lock when the template is catalog-managed.
Template mode and phone number
Template lists are loaded from your connected WhatsApp Business account. The workflow must be linked to a WhatsApp phone number (the bot’s associated business line in Pingmee). If no phone number is configured, changing the template Source or clicking refresh on the template list shows: You must select a phone number first — configure the bot’s phone number in the host app before editing templates.
Variables
Body and header fields accept placeholders from connected upstream nodes. The form offers a variable picker built from the graph. See Variables.
Wait for user response
When enabled:
- The flow waits for an inbound message after this send.
- A timeout sub-node may run if no reply arrives in time.
- A fallback sub-node may run when the user does not select an expected button.
Configure those sub-nodes on the canvas after enabling this option. See Sub-nodes.
Flow behavior
- Input: Typically follows a trigger or earlier action; uses conversation context from the platform.
- Output: One default edge to the next node; additional edges from sub-nodes (timeout/fallback) when configured.
- RTL: Message preview on the canvas picks direction from text content (Hebrew/Arabic → RTL).
Examples
Simple notification
- Set Message Type to Simple.
- Write the Body (optionally insert variables).
- Leave Wait for user response off.
- Connect to the next action.
Ask a question
- Write the Body with the question.
- Enable Wait for user response.
- Add Buttons for expected answers (optional).
- Configure the timeout and fallback sub-nodes on the canvas.
Related
- Nodes drawer — add WhatsApp from the action section
- Variables
- Sub-nodes
- Messenger — similar message form for Facebook