Short answer: Drop the "WhatsApp Business → Send Image" 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 | To Phone Number. e.g. "+1234567890" |
Image URL imageUrl | url | Required | Image URL. e.g. "https://example.com/image.jpg" |
Caption caption | string | Optional | Caption. e.g. "Check out this image!" |
{"to": "+1234567890","imageUrl": "https://example.com/image.jpg","caption": "Check out this image!"}
{"messages": [{"id": "wamid.ghi789"}],"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.