PRO Send WhatsApp - Captain icon

PRO Send WhatsApp - Captain

Node to Send WhatsApp

PRO Send WhatsApp - Captain

AI-generated

Overview

This node sends WhatsApp messages as part of a campaign using a specified WhatsApp provider or rotary mode. It supports sending personalized text messages with optional media files, managing message sending frequency per mobile number, and tagging users based on message status. It can wait until all messages are sent before completing execution, making it suitable for bulk messaging campaigns, customer engagement, and automated WhatsApp communication workflows.

Use Case Examples

  1. Sending a personalized WhatsApp message to a list of users in a campaign.
  2. Using rotary mode to distribute messages across multiple WhatsApp providers.
  3. Adding tags to users after sending messages and scheduling tag removal.
  4. Ensuring messages are sent only once per mobile number within a specified time frame.

Properties

Name Meaning
Select a Campaign Selects the campaign from which to send WhatsApp messages.
Rotary Mode Enables rotary mode to distribute messages across providers.
WhatsApp Provider Selects the WhatsApp provider to use when rotary mode is disabled.
WhatsApp Name Name of the WhatsApp campaign.
WhatsApp Message Text content of the WhatsApp message, supports expressions for dynamic content.
File URL (Optional) URL of an optional media file (image, video, etc.) to send with the message.
Wait Until All Messages Sent. If true, the node waits until all messages are confirmed sent before finishing.
Tag Settings Settings for tagging users after sending messages, including tag name and removal timing.
Once Per Mobile Number If true, ensures messages are sent only once per mobile number 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 If true, ignores frequency capping restrictions.
Ignore DND If true, ignores Do Not Disturb settings.
Users Specifies users to send messages to; if blank, uses users from the previous node.

Output

JSON

  • usersAndText - Array of user message objects including userId, text, fileUrl, and outputResult.
  • whatsAppName - Name of the WhatsApp campaign used.
  • campaign_id - ID of the selected campaign.
  • providerTitle - Selected WhatsApp provider title.
  • tagName - Tag name used for tagging users.
  • once - Boolean indicating if messages are sent once per mobile number.
  • onceDaysToRemove - Days after which users can receive messages again.
  • uuid - Unique identifier for the batch of messages sent.
  • ignoreFC - Boolean indicating if frequency capping is ignored.
  • ignoreDND - Boolean indicating if Do Not Disturb is ignored.
  • executionId - Execution ID of the current workflow run.
  • workflowName - Name of the workflow executing the node.
  • rotaryMode - Boolean indicating if rotary mode is enabled.
  • tagToRemoveDays - Days after which to remove the tag.
  • tagToRemoveHours - Hours after which to remove the tag.
  • tagToRemoveMinutes - Minutes after which to remove the tag.

Dependencies

  • Requires environment variables CDP_URL and UNEXO_API_KEY for API access and authorization.

Troubleshooting

  • Common issues include API request failures due to incorrect or missing API keys or environment variables. Ensure CDP_URL and UNEXO_API_KEY are correctly set.
  • Message sending may fail if the campaign or WhatsApp provider is not properly selected or available.
  • If 'Wait Until All Messages Sent' is enabled, the node may take longer to complete due to polling for message status; network issues can cause delays or timeouts.
  • Errors during HTTP requests are retried up to 3 times with delays; persistent failures indicate connectivity or API issues.

Links

Discussion