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 WhatsApp messages. Specifically, the Send meeting event operation allows users to create and send a calendar event invitation via WhatsApp. This is useful for scheduling meetings, appointments, or any event where you want to notify participants directly through WhatsApp.

Typical use cases include:

  • Sending meeting invites to clients or team members.
  • Notifying customers about upcoming events or appointments.
  • Sharing event details including time, location, and call type (voice/video).

Example: Automatically sending a meeting event invite to a customer after they book an appointment on your website.

Properties

Name Meaning
WhatsApp number The target Wassenger Number ID used to send the message.
Target Type of chat to send the message to: Phone, 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.
Event Name Name or title of the event (max 100 characters).
Event Description Optional description of the event (up to 2048 characters).
Event Date and Time Date and time of the event in ISO 8601 format.
Event Location Optional location name for the event (up to 255 characters).
Location Coordinates Optional geographical coordinates (latitude and longitude) for the event location.
Meeting Call Type Type of WhatsApp call for the event meeting: No Call, Voice Call, or Video Call.
Options Collection of additional options such as:
- 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.)
Message Expiration Defines message TTL (time-to-live) with options:
- Seconds
- Duration (e.g., 1h, 30m)
- Specific date/time expiration
Mark Chat as Read Whether to send a read receipt after message delivery (blue double-check).
Typing simulation Seconds to simulate typing or recording status before sending (0 disables).
Quote Message Message ID to quote when sending this message (must be in same conversation).
Strict Message Order Ensures messages are sent in strict order; useful for chatbots or sequences. Not compatible with live or never queue modes.

Output

The node outputs JSON data representing the result of the send meeting event operation. This typically includes confirmation details such as message IDs, status, timestamps, and any error information if applicable.

If binary data were involved (not in this operation), it would represent media files or attachments, but here the output is purely JSON describing the sent event message.

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.
  • Some properties load dynamic options from the API, such as available devices, groups, channels, labels, team agents, and departments.
  • Proper configuration of these resources in Wassenger is necessary for successful message delivery.

Troubleshooting

  • Invalid phone number format: Ensure phone numbers follow the E.164 international format (e.g., +1234567890). The node validates this with regex.
  • Missing required fields: Event name, date/time, and target identifiers (phone/group/channel) are mandatory.
  • API authentication errors: Verify that the API key credential is correctly set up and has permissions.
  • Delivery failures due to rate limits: Using real-time delivery mode ("live") with high message volume can cause bans by WhatsApp. Use queue modes appropriately.
  • Incorrect IDs for groups, channels, agents, or departments: These must be valid and exist in Wassenger; otherwise, the API will reject the request.
  • Typing simulation conflicts: Setting typing simulation with incompatible delivery modes (like live or never queue) may cause unexpected behavior.
  • Strict message order incompatibility: Cannot be used with live or never queue delivery modes.

To resolve errors, check the error messages returned in the node output JSON and verify all input parameters and credentials.

Links and References

Discussion