Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node allows sending poll messages via WhatsApp using the Wassenger API. It is designed to create interactive polls within WhatsApp chats, groups, or channels, enabling recipients to vote on predefined options. This functionality is useful for gathering opinions, conducting surveys, or making group decisions directly through WhatsApp conversations.

Practical examples include:

  • Sending a poll to a customer support group to prioritize issues.
  • Creating a quick survey in a marketing channel to gauge interest in new products.
  • Polling team members in a group chat about meeting times or project preferences.

Properties

Name Meaning
WhatsApp number The target Wassenger Number ID used to send the message. This identifies which WhatsApp number/account will deliver the poll.
Target Type of target chat where the poll will be sent. Options: Phone (individual), Group, 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".
Poll Question The question or title text for the poll. Maximum length 250 characters.
Poll Options The list of poll options (minimum 2, maximum 10). Each option is a string up to 100 characters.
Options Additional message options including:
- Priority: Normal, High, Low
- Label: Custom label to categorize the message
- Reference ID: Custom reference 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 retries
- Chat Actions: Post-delivery actions like assign chat, resolve chat, add/remove labels, set metadata, etc.
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 delivery (blue double-check).
Typing simulation Seconds to simulate typing or recording status before sending (0 disables). Range 2-30 seconds.
Quote Message Message ID to quote when sending this poll (must be from the same conversation). Hexadecimal string 18-32 characters.
Strict Message Order Boolean to ensure messages are sent in strict order. Useful for chatbots and sequences. Not compatible with live mode or never queue delivery.

Output

The node outputs JSON data representing the response from the Wassenger API after sending the poll message. This typically includes details such as message IDs, status, timestamps, and any errors encountered.

No binary data output is expected from this operation.

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 (e.g., devices, groups, channels, agents, labels) which require appropriate API permissions and connectivity.
  • Proper configuration of the WhatsApp number and associated environment in Wassenger is necessary.

Troubleshooting

  • Invalid phone number format: Ensure the phone number is in E.164 format (e.g., +1234567890). The node validates this with a regex.
  • Missing required fields: Poll question and at least two poll options must be provided.
  • Delivery failures: Using real-time mode ("live") or disabling queue may increase risk of message bans if sending high volumes rapidly. Use queue modes appropriately.
  • Agent or department IDs invalid: When assigning chats or actions, ensure IDs are valid 24-character hexadecimal strings.
  • Message quoting errors: Quoted message ID must exist in the same conversation and match the required format.
  • API authentication errors: Verify the API key credential is correct and has sufficient permissions.
  • Exceeded retries: If message delivery fails repeatedly, check network connectivity and API limits.

Links and References

Discussion