Short answer: Drop the "WhatsApp Business → Send 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 Phone Number to | phone | Required | Recipient phone number with country code |
Message Text text | string | Required | Message Text. e.g. "Hello from WhatsApp!" |
{"to": "+1234567890","text": "Hello from WhatsApp!"}
{"contacts": [{"input": "+1234567890","wa_id": "1234567890"}],"messages": [{"id": "wamid.abc123"}],"messaging_product": "whatsapp"}
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.