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 multimedia messages via the Wassenger WhatsApp API. It supports sending various types of media (images, documents, videos, audio) to individual phone numbers, groups, or channels on WhatsApp. The node is useful for automating communication workflows such as customer support, marketing campaigns, notifications, and interactive chatbots that require rich media content.
Practical examples include:
- Sending promotional videos or brochures to customers.
- Delivering event invitations with images to WhatsApp groups.
- Sharing product catalogs or audio messages in broadcast channels.
- Automating multimedia responses in chatbot conversations.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target Wassenger Number ID used for message delivery. This identifies the WhatsApp account/device from which the message will be sent. |
| Target | Type of target chat: Phone (individual), Group, or Channel. |
| Phone Number | Target phone number in international E.164 format (e.g., +1234567890). Required if Target is "Phone". |
| Group ID | ID of the target group chat (e.g., 12345678902401234@g.us). Required if Target is "Group". |
| Channel ID | ID of the target channel (e.g., 12345678902402200@newsletter). Required if Target is "Channel". |
| Message | Text message to send. Used when sending text or scheduled messages. |
| File URL | URL of the media file to send (image, document, video, audio). Required for sending multimedia messages. |
| 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 sending without queue) - Delivery Queue Mode (default, always queue, never queue, opportunistic) - Maximum Retries (number of delivery attempts) - Chat Actions (post-delivery actions like assign chat, resolve, add/remove labels or metadata) |
| Message Expiration | Defines 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 are read after delivery (blue double-check). Requires WhatsApp read confirmation enabled. |
| Typing simulation | Seconds to simulate typing or recording status before sending (2-30 seconds). Set 0 to disable. |
| Quote Message | Message ID to quote when sending this message (18-32 hex characters). Can only quote messages in the same conversation. |
| Strict Message Order | Boolean to ensure messages are sent in strict order to the target chat. Useful for chatbots and sequences. Not compatible with live mode or "never queue" delivery options. |
Output
The node outputs a JSON object representing the response from the Wassenger API after attempting to send the multimedia message. This typically includes details about the message delivery status, message ID, timestamps, and any errors encountered.
If binary data is involved (e.g., media files), the node handles sending via URLs rather than outputting binary content itself.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on external services provided by Wassenger for WhatsApp messaging.
- Proper configuration of the Wassenger API key in n8n credentials is necessary.
- Internet access is required to fetch media files from provided URLs.
Troubleshooting
- Invalid phone number format: Ensure phone numbers are in E.164 format (e.g., +1234567890). The node validates this with regex.
- Missing required fields: For example, if Target is "Group", Group ID must be provided; similarly for "Channel".
- Media URL issues: The media URL must be valid and accessible. Invalid URLs or unsupported media types will cause failures.
- Delivery queue misconfiguration: Using real-time delivery ("never queue") at high message rates may lead to WhatsApp bans. Use queue modes appropriately.
- Agent or Department IDs: When assigning chats post-delivery, ensure valid 24-character hexadecimal IDs are used.
- Message quoting restrictions: Quoted message IDs must be valid and belong to the same conversation.
- Read receipt not working: WhatsApp privacy settings might disable read confirmations, making the "Mark Chat as Read" option ineffective.
- Typing simulation limits: Values outside 2-30 seconds range are ignored or cause errors.
Common error messages usually relate to invalid parameters, authentication failures, or rate limiting by WhatsApp/Wassenger API. Review error details in the node output JSON for troubleshooting.