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 interacts with the Wassenger WhatsApp API to manage WhatsApp messaging operations. Specifically, for the "Send messages" resource and the "Delete votes in a poll" operation, it allows users to remove votes from a specific poll message within a WhatsApp chat.
Common scenarios where this node is beneficial include:
- Managing interactive polls sent via WhatsApp by removing unwanted or incorrect votes.
- Moderating group or channel polls to maintain accurate results.
- Automating poll management workflows in customer engagement or marketing campaigns.
Practical example:
- A business sends a poll to customers asking for feedback on products. If a vote was submitted incorrectly or needs to be retracted, this node can delete that vote programmatically based on the poll message ID.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target Wassenger Number ID used for sending the message. This identifies which WhatsApp number/account will perform the action. |
| Target | Type of target chat: Phone (individual), Group, or Channel. Determines where the poll vote deletion applies. |
| 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 group chat (e.g., 12345678902401234@g.us). Required if Target is "Group". |
| Channel ID | The ID of the target channel (e.g., 12345678902402200@newsletter). Required if Target is "Channel". |
| Poll Message ID | The unique identifier of the poll message from which votes should be deleted. Must be 18 to 32 hexadecimal characters. |
| Options | Collection of optional settings including: - Priority (Normal, High, Low) - Label (custom categorization) - Reference ID - Team Agent (send on behalf of an agent) - Live mode (real-time delivery) - Delivery queue mode - Maximum retries - Chat actions (assign, resolve, label, metadata, etc.) after message delivery |
| Message Expiration | Defines time-to-live (TTL) for the message with options to expire after seconds, duration (e.g., 1h), or at a specific date/time. |
| Mark Chat as Read | Boolean to notify WhatsApp that previous unread messages are read after this operation (blue double-check). |
| Typing simulation | Seconds to simulate typing or recording status before delivery (0 disables). Useful for more natural interaction timing. |
| Quote Message | Message ID to quote when sending the message. Must be 18-32 hex characters and in the same conversation. |
| Strict Message Order | Boolean to ensure messages are sent in strict order. Not compatible with live mode or never queue delivery. Useful for chatbots or sequences. |
Output
The node outputs JSON data representing the result of the delete poll vote operation. This typically includes confirmation of success or details about the deleted vote. The exact structure depends on the Wassenger API response but generally confirms that the specified vote was removed from the poll message.
No binary data output is involved in this operation.
Dependencies
- Requires an active Wassenger WhatsApp API key credential configured in n8n.
- Depends on the Wassenger service being accessible and properly authenticated.
- Uses dynamic loading methods to fetch options such as devices, groups, channels, labels, team agents, and departments.
- No additional external dependencies beyond the Wassenger API.
Troubleshooting
- Invalid Poll Message ID: Ensure the pollMessageId matches the required hexadecimal format (18-32 characters). Errors here indicate invalid or malformed IDs.
- Target Mismatch: Selecting a target type (phone, group, channel) without providing the corresponding ID or number will cause errors. Make sure the correct target property is filled.
- Permission Issues: The API key must have permissions to modify poll votes. Insufficient permissions may cause authorization errors.
- Rate Limits and Delivery Modes: Using real-time delivery modes ("live" or "never queue") with high message volumes can lead to temporary bans or failures. Use queue modes appropriately.
- Typing Simulation Conflicts: Setting typing simulation with incompatible delivery modes (like live mode) may cause unexpected behavior.
- Chat Actions Misconfiguration: When using post-delivery chat actions, ensure required fields like agent or department IDs are valid and provided.