Short answer: Drop the "Twilio WhatsApp → Send WhatsApp Message" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
To Number to | phone | Required | Recipient phone with country code |
Message body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
{"to": "+14155552671","body": "e.g. Hi there, thanks for reaching out."}
{"to": "whatsapp:+14155552671","sid": "SM123","body": "Hello!","status": "queued","date_created": "2026-04-11T10:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.