Messenger
Send Facebook Messenger messages with optional wait-for-reply.
The Messenger action sends outbound Facebook Messenger content. It uses the shared Message form: message type, body with variables, and optional wait for user response (with answer/fallback/timeout sub-nodes like WhatsApp).
When to use
- Reply in standard conversation flows (Direct Message).
- Social workflows: public Reply to Post or Private Reply after a Facebook comment trigger.
- Pause until the user answers before continuing.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Message Type | Controls channel behavior (see below) | Match Meta rules for DM vs comment vs private reply |
| Body | Main text; supports variables | Always |
| Wait for user response | Pauses until inbound reply; enables sub-nodes | Surveys, confirmations, menus (shown for DM and Private Reply types) |
| Description | Canvas note | Documentation |
Message Type
| Option | When to use |
|---|---|
| Direct Message (DM) | Normal Messenger thread |
| Reply to Post | Public comment thread on a post |
| Private Reply | Private message to commenter; enables Wait for user response when selected |
In social-channel workflows (comment triggers), Direct Message is not listed; use Reply to Post or Private Reply.
Wait for user response
When enabled:
- Flow waits for an inbound message after this send.
- Configure answer, fallback, and timeout sub-nodes on the canvas.
Flow behavior
- Input: After trigger or prior actions.
- Output: Default parent edge, or per sub-node handles when waiting for response / buttons.
- Up to 13 answer sub-nodes when using interactive branches.
Examples
Simple DM
- Message Type → Direct Message (DM).
- Write Body; leave Wait for user response off.
- Connect to the next action.
Comment trigger → private reply
- Start from Facebook Trigger.
- Message Type → Private Reply.
- Write Body; enable Wait for user response if the next step needs the user’s answer.