Short answer: Drop the "WhatsApp Business → Send Media" 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 |
|---|---|---|---|
Recipient phone to | string | Required | — |
Media Type type | options | Required | — |
Media URL link | string | Required | — |
Caption (image/video/document) caption | string | Optional | — |
Filename (document only) filename | string | Optional | — |
{"to": "{{trigger.to}}","type": "{{trigger.type}}","link": "{{trigger.link}}","caption": "{{trigger.caption}}","filename": "{{trigger.filename}}"}
{"messages": [{"id": "wamid.abc"}]}
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.