Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node integrates with the Wassenger WhatsApp API to send various types of messages and interact with WhatsApp chats programmatically. Specifically, the Send meeting confirmation operation under the Send messages resource allows users to respond to event invitations by sending a confirmation message (accept or decline) to a specified WhatsApp chat.

Typical use cases include:

  • Automatically confirming or declining calendar event invitations received via WhatsApp.
  • Integrating WhatsApp event confirmations into CRM or scheduling workflows.
  • Streamlining communication for meetings by automating responses based on external triggers.

For example, after receiving an event invitation message in WhatsApp, this node can be used to send an acceptance or decline response automatically, helping teams manage their schedules efficiently.

Properties

Name Meaning
WhatsApp number The target Wassenger Number ID used to send the message. This identifies which WhatsApp number/account will deliver the confirmation.
Target Type of target chat: Phone, Group, or Channel. For meeting confirmation, the target is typically a phone number chat.
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 channel ID to send the message to (e.g., 12345678902402200@newsletter). Required if Target is "Channel".
Event Message ID The unique identifier of the event message to respond to. Must be a hexadecimal string between 18 and 32 characters.
Response The response to the event invitation: either "Accept Invitation" or "Decline Invitation".
Options Additional optional settings including:
- Priority (Normal, High, Low)
- Label (custom categorization label)
- Reference ID (custom reference)
- Team Agent (send on behalf of an agent)
- Live mode (real-time delivery)
- Delivery queue mode
- Maximum retries
- Post-delivery chat actions (assign, resolve, label, metadata, etc.)
Message Expiration Defines a time-to-live (TTL) for the message, specifying when it should expire. Can be set as seconds, duration (e.g., "1h"), or specific date/time.
Mark Chat as Read Whether to notify WhatsApp that previous unread messages are read after sending this message (blue double-check).
Typing simulation Seconds to simulate typing or recording status before sending the message (0 disables). Useful for more natural interaction.
Quote Message Message ID to quote when sending the confirmation, allowing the confirmation to reference a specific prior message.
Strict Message Order Ensures messages are sent in strict order to the chat, useful for chatbots or sequences. Not compatible with live or never-queue delivery modes.

Output

The node outputs JSON data representing the result of the confirmation message operation. This typically includes details such as message IDs, status, timestamps, and any relevant metadata returned by the Wassenger API.

If binary data were involved (not applicable here), it would represent media content or files sent/received.

Dependencies

  • Requires an active Wassenger WhatsApp API account with a valid API key credential configured in n8n.
  • The node depends on the Wassenger service to send WhatsApp messages and handle event confirmations.
  • Proper configuration of WhatsApp numbers, groups, channels, and team agents within Wassenger is necessary for correct operation.
  • Network connectivity to Wassenger API endpoints is required.

Troubleshooting

  • Invalid phone number format: Ensure the phone number is in E.164 format (e.g., +1234567890). The node validates this and will error if incorrect.
  • Invalid event message ID: The event message ID must be a hexadecimal string of length 18, 20, 24, or 32 characters. Errors occur if this is malformed.
  • Missing required fields: Fields like WhatsApp number, target, and event message ID are mandatory. Omitting them causes errors.
  • Delivery failures: Using real-time delivery mode ("live") or disabling queuing while sending many messages rapidly may lead to temporary bans or message loss. Use queue modes appropriately.
  • Agent or department assignment errors: When using post-delivery chat actions, ensure agent and department IDs are valid and correctly formatted.
  • API authentication errors: Verify the API key credential is correctly set up and has sufficient permissions.
  • Message quoting limitations: Quoting messages only works within the same conversation; otherwise, errors may occur.

Links and References

Discussion