Overview
This node enables sending WhatsApp messages in bulk through a selected campaign and provider. It is designed to integrate with an external service that manages campaigns, WhatsApp providers, and message dispatching. The node supports personalized text messages using expressions referencing previous node data, optional media attachments via file URLs, tagging users, and controlling message frequency per mobile number.
Common scenarios include:
- Marketing teams sending promotional WhatsApp campaigns to targeted user lists.
- Customer support automations delivering updates or notifications via WhatsApp.
- Workflows requiring personalized WhatsApp outreach with dynamic content and media.
Practical example:
A workflow fetches a list of users from a CRM, then uses this node to send each user a personalized WhatsApp message including their first name, optionally attaching an image URL, and tagging them for follow-up.
Properties
| Name | Meaning |
|---|---|
| Select a Campaign | Choose a predefined campaign from the list to associate with the messages sent. |
| WhatsApp Provider | Select the WhatsApp service provider to use for sending messages. |
| WhatsApp Name | Name of the WhatsApp campaign/message batch being sent. |
| WhatsApp Message | Text content of the WhatsApp message; supports expressions to personalize per user. |
| File URL (Optional) | URL of a media file (image, video, etc.) to attach and send along with the message. |
| Wait Until All Messages Sent. | Boolean flag to wait for confirmation that all messages have been sent before continuing. |
| Add Tag | Tag name to add to users receiving the message, useful for categorization or tracking. |
| Once Per Mobile Number | If true, ensures each mobile number receives the message only once within a specified period. |
| When Can Users Receive Again (In days, 0 for never)? | Number of days after which a user can receive messages again if "Once Per Mobile Number" is enabled. |
| Ignore FC | Boolean flag to ignore some internal filtering condition (likely related to message sending). |
| Users | Comma-separated string of user identifiers to send messages to; leave blank to use input data. |
Output
The node outputs JSON data representing the response from the external API after attempting to send the WhatsApp messages. This includes status information about the batch send operation or completion status if waiting for all messages to be sent.
If "Wait Until All Messages Sent." is enabled, the output will contain detailed results confirming message delivery completion.
No binary data output is produced by this node.
Dependencies
Requires environment variables:
CDP_URL: Base URL of the external API managing campaigns and WhatsApp messaging.UNEXO_API_KEY: API key used for authorization with the external service.
The node makes HTTP requests to the external API endpoints for:
- Fetching campaign names.
- Fetching WhatsApp provider titles.
- Sending WhatsApp message batches.
- Checking message send completion status.
Proper configuration of these environment variables and network access to the API endpoints is necessary.
Troubleshooting
Common issues:
- Missing or incorrect API key or base URL environment variables will cause authentication failures.
- Network connectivity problems to the external API will result in request errors.
- Invalid campaign or provider selections may cause the API to reject requests.
- Expression syntax errors in the WhatsApp Message property could lead to empty or malformed messages.
Error messages and resolutions:
- Authorization errors: Verify that
UNEXO_API_KEYis correctly set and has sufficient permissions. - Timeout or maximum retry reached when waiting for message completion: Check API responsiveness and consider disabling the wait option if not needed.
- "Maximum retry attempts reached." logged: Indicates the node waited but did not receive confirmation that all messages were sent; verify API health and message queue status.
- Authorization errors: Verify that
Links and References
- No direct links provided in the source code. For more information, consult the documentation of the external WhatsApp campaign management API referenced by the environment variables.