Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node integrates with the Wassenger WhatsApp API to send a reaction emoji to a specific WhatsApp message. It allows users to react to messages in individual chats, groups, or channels by specifying the target and the message ID to react to. This is useful for automating engagement on WhatsApp conversations, such as acknowledging messages, expressing emotions, or managing chat interactions programmatically.

Common scenarios:

  • Automatically reacting with a thumbs-up emoji to confirm receipt of a message.
  • Removing a previous reaction by sending a special "-" emoji.
  • Reacting to messages in group chats or broadcast channels to automate feedback or moderation workflows.

Practical example:

  • A customer support chatbot reacts with a "👍" emoji to every incoming customer message to indicate it has been received and is being processed.

Properties

Name Meaning
WhatsApp number The Wassenger Number ID used to send the reaction (the WhatsApp account/device). Loaded dynamically from available devices.
Target Type of target chat where the reaction will be sent. Options: Phone (individual), Group, 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 ID to React to The unique ID of the WhatsApp message to which the reaction emoji will be applied. Must be 18-32 hexadecimal characters.
Emoji Reaction The emoji character to send as a reaction (e.g., 👍). Use "-" to remove an existing reaction. Maximum length 10 characters.
Options Collection of optional settings including:
- Priority (Normal, High, Low)
- Label (custom categorization label)
- Reference ID (custom message reference)
- 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
- Chat Actions (assign, resolve, label, metadata operations after delivery)
Message Expiration Defines time-to-live (TTL) for the message reaction. Can specify expiration in seconds, duration string (e.g., "1h"), or exact date/time.
Mark Chat as Read Boolean flag to notify WhatsApp that previous unread messages in the chat are read after sending the reaction (blue double-check).
Typing simulation Number of seconds (0-30) to simulate typing or recording status before sending the reaction. 0 disables simulation.
Quote Message Optional message ID to quote when sending the reaction. Must be in the same conversation.
Strict Message Order Boolean to ensure strict order of messages sent to the chat. Useful for chatbots or sequences. Not compatible with live mode or never queue options.

Output

The node outputs JSON data representing the result of the reaction operation. This typically includes confirmation details such as message IDs, status, or error information if the reaction failed.

No binary data output is involved.

Example output JSON structure (conceptual):

{
  "messageId": "abcdef1234567890abcdef12",
  "status": "sent",
  "target": "+1234567890",
  "reactionEmoji": "👍"
}

Dependencies

  • Requires an active Wassenger WhatsApp API integration with a valid API key credential configured in n8n.
  • Dynamic loading of options depends on API calls to fetch devices, groups, channels, labels, team agents, and departments.
  • Proper WhatsApp number/device setup in Wassenger platform.
  • Network connectivity to Wassenger API endpoints.

Troubleshooting

  • Invalid phone number format: Ensure the phone number is in E.164 format (e.g., +1234567890). The node validates this with a regex.
  • Invalid message ID: The message ID must be 18-32 hexadecimal characters. Errors occur if the ID is malformed or does not exist.
  • Reaction emoji issues: Use valid emojis supported by WhatsApp. To remove a reaction, use the "-" character exactly.
  • Delivery failures: If using real-time delivery mode ("live" or "never queue") and sending many messages rapidly, WhatsApp may ban the number. Use queue modes appropriately.
  • Permission errors: Make sure the API key has permissions to send reactions and access the specified device/group/channel.
  • Typing simulation conflicts: Using typing simulation with strict message order or live mode may cause unexpected behavior; disable incompatible options.
  • Chat actions misconfiguration: When assigning chats or setting metadata, ensure required fields like agent or department IDs are correctly provided.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion