Automations · Nodes · action
Ask WhatsApp interactive
action.whatsapp_ask_interactive · action
Send reply buttons or a list, wait for the tap, then continue on the matching option port.
When to use
- Offer reply buttons or a list and continue on the matching option port.
- Prefer Ask over send + wait when the answer should branch the workflow.
- This is Automations interactive messaging — not Meta WhatsApp Flows.
Configuration
| Field | Required | Notes |
|---|---|---|
| accountId | no | Channel account; leave empty to use context when available |
| interactiveType | no | button (reply buttons) or list |
| bodyText | no | Message body; expressions allowed |
| headerText | no | Optional header (list); expressions allowed |
| footerText | no | Optional footer (list); expressions allowed |
| listButtonLabel | no | CTA label on the list message |
| buttons | no | Reply buttons: id (static) + title (max 3) |
| sections | no | List sections with rows: id (static), title, optional description |
| interactive | no | Optional power override — prefer buttons/sections in the portal |
| timeoutSeconds | no | Wait timeout in seconds (default 86400) |
Inputs
Upstream node output and execution context (contact, account, variables).
Outputs
After the customer taps (or timeout): replyId, replyTitle, interactiveType, inboundMessageId, outboundMessageId / messageId, timedOut. Insert value paths use nodes.{id}.*.
Execute step (editor)
| Eligible? | Notes |
|---|---|
| Disabled | Needs multi-branch or wait/resume context — use a full Test run. |
See Test, Execute, debug, listen and limitations.
Common errors
| Symptom | Cause | Fix |
|---|---|---|
| Interactive wait never resumes | Customer sent free text, or wrong contact/outbound correlation | Only button_reply / list_reply resume; set expected outbound message id when using wait-only. |
| INTERACTIVE_WAIT_CONFLICT | Another interactive wait is already open for this contact | Wait for the other run to finish or time out before opening another Ask/wait. |
| Send failed on Test/Run | Outside window, bad template, or missing contact | Use template outside window; ensure contact/account in context. |
| Execute succeeds but nothing delivered | Execute is dry-run for channel sends | Use full Test run / Run now. |
Example
Message-received trigger → Ask interactive (2+ option ids) → connect each option / default / timeout → Publish → customer taps a button.