Package Information
Available Nodes
Documentation generating…
Documentation
@cardtunic/n8n-nodes-whatsapp-cloud-api
This is an n8n community node for sending messages with the WhatsApp Cloud API.
n8n is a workflow automation platform.
Installation
Follow the community node installation guide.
Install this package by name:
@cardtunic/n8n-nodes-whatsapp-cloud-api
Operations
Message
- Send structured text, media, location, contact, reaction, template, and interactive messages
- Mark an incoming message as read
- Mark an incoming message as read and display a typing indicator
The node uses the WhatsApp Cloud API /messages endpoint. Marketing-message and encrypted-message endpoints are not included.
Media
- Upload an n8n binary file through the WhatsApp Media API
- Return the uploaded media ID for reuse in later message operations
Credentials
The credential requires these values from your Meta app's WhatsApp API setup page:
- Access Token: A token with
whatsapp_business_messagingpermission for sending andwhatsapp_business_managementpermission for template discovery. - WhatsApp Business Phone Number ID: The ID of the sender phone number, not the displayed phone number.
- WhatsApp Business Account ID: The WABA ID containing the approved message templates.
See Meta's Cloud API setup guide for instructions.
Usage
Add the WhatsApp Cloud API node to a workflow and select Message > Send Message. Choose a message type and configure the fields shown for that type.
The structured sender supports:
- Text messages with optional URL previews
- Audio, document, image, sticker, and video messages by n8n binary file, uploaded media ID, or public URL
- Location, reaction, and contact messages
- Templates with header, body, and button components
- Reply buttons, lists, catalog messages, products, product lists, Flows, call-permission requests, order details, and order-status interactive messages
- Replies using an optional source message WAMID
Attachments
For automatic attachment upload, connect a node that outputs binary data, select an audio, document, image, sticker, or video message, and choose Binary File as the media source. Set Input Binary Field to the binary property name, typically data.
The node uploads the file to /media, inserts the returned media ID into the message, and then sends the message through /messages. The output is the final message response. If upload succeeds but sending fails, the uploaded media remains in WhatsApp storage.
Use Media > Upload when you want the media ID explicitly or intend to reuse one upload in multiple messages. The operation returns:
{
"id": "WHATSAPP_MEDIA_ID"
}
The filename and MIME type are read from n8n's binary metadata. Both can be overridden when the metadata is missing or incorrect. Automatic binary upload currently applies to top-level attachments; template media parameters and interactive headers continue to use media IDs or URLs.
When Template is selected, the node loads approved templates from the configured WhatsApp Business Account. After choosing a template, the language dropdown shows its approved language variants. Expressions can still supply a template name or language code directly.
Recipient numbers must include the country code without spaces or a leading +, for example 15551234567.
Free-form messages can only be sent during the 24-hour customer service window after the recipient contacts your business. Use an approved message template to initiate or resume a conversation outside that window.
Meta permits at most 10 rows across all sections in one list message. Row IDs must be unique because WhatsApp returns the selected row ID in the recipient's reply webhook.
Use Mark Message as Read with an incoming message WAMID to send a read receipt. Mark Read and Show Typing sends the same receipt together with a text typing indicator. Delivery status is generated by WhatsApp and must be observed through webhooks; it cannot be set through the /messages endpoint.
Compatibility
This package targets WhatsApp Cloud API v26.0 and n8n 1.60.0 or later.