Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node enables sending WhatsApp text messages through the Wassenger API. It supports sending messages to individual phone numbers, groups, or channels associated with a selected WhatsApp number (device). The node is useful for automating WhatsApp communications such as customer support replies, marketing broadcasts, notifications, or chatbot interactions.
Practical examples:
- Sending a personalized text message to a customer's phone number.
- Broadcasting announcements to a WhatsApp group or channel.
- Automating chat responses with typing simulation and message quoting features.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | Select the target Wassenger Number ID (WhatsApp device) used to send the message. |
| Target | Choose the type of recipient: Phone (individual), Group, or Channel. |
| Phone Number | The recipient's phone number in international E.164 format (e.g., +1234567890). Required if Target is Phone. |
| Group ID | The ID of the target WhatsApp group chat (e.g., 12345678902401234@g.us). Required if Target is Group. |
| Channel ID | The ID of the target WhatsApp channel (e.g., 12345678902402200@newsletter). Required if Target is Channel. |
| Message | The text content of the message to be sent (up to 6000 characters). |
| Options | Collection of optional settings including: - Priority (Normal, High, Low) - Label (custom categorization tag) - Reference ID (custom identifier) - Team Agent (send on behalf of an agent) - Live mode (real-time delivery without queue) - Delivery Queue Mode (default, always queue, never queue, opportunistic) - Maximum Retries (0-100) - Chat Actions (post-delivery actions like assign chat, resolve, add/remove labels or metadata) |
| Message Expiration | Define time-to-live (TTL) for the message using seconds, duration string (e.g., "1h"), or specific date/time. |
| Mark Chat as Read | Boolean to notify WhatsApp that previous unread messages will be marked as read after this message is delivered (blue double-check). |
| Typing simulation | Number of seconds (0-30) to simulate typing or recording status before sending the message. Zero disables simulation. |
| Quote Message | Message ID (18-32 hex characters) to quote when sending the message, allowing replies within the same conversation. |
| Strict Message Order | Boolean to ensure messages are sent in strict order to the target chat. Useful for chatbots or sequences but incompatible with live mode or never queue options. |
Output
The node outputs JSON data representing the result of the message sending operation. This typically includes details about the sent message such as message ID, status, timestamps, and any metadata returned by the Wassenger API.
If binary data were involved (not applicable here), it would represent media files or attachments sent or received.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- Some properties load dynamic options from the API, such as available devices, groups, channels, agents, labels, and departments.
- Proper WhatsApp number setup and permissions on Wassenger platform are necessary.
Troubleshooting
- Invalid phone number format: Ensure phone numbers follow the E.164 format (e.g., +1234567890). The node validates this and will error if invalid.
- Missing required fields: Depending on the target type, either phone number, group ID, or channel ID must be provided.
- Delivery failures due to rate limits: Using real-time delivery mode ("live" or "never queue") at high message volumes may cause bans or throttling by WhatsApp. Use queue modes appropriately.
- Agent or department IDs invalid: When assigning chats or performing actions, ensure valid 24-character hexadecimal IDs are used.
- Message quoting errors: Quoted message IDs must be valid and belong to the same conversation.
- Read receipt not working: The "Mark Chat as Read" option requires WhatsApp privacy settings to allow read confirmations.
- Strict order conflicts: Enabling strict message order is incompatible with live mode or never queue options; avoid combining these.