Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node interacts with the Wassenger WhatsApp API to retrieve detailed information about a specific chat associated with a WhatsApp number. It is particularly useful for scenarios where you need to fetch comprehensive chat data, including messages, notes, and participants, for monitoring, analytics, or customer support purposes.

Practical examples include:

  • Fetching all messages and notes from a particular chat to display in a CRM.
  • Retrieving participant details of a group chat for administrative tasks.
  • Synchronizing chat history for backup or auditing.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) from which to retrieve the chat details.
Chat ID The unique identifier of the chat. For individual users, it looks like 447362053576@c.us; for groups, 44736205357600000000@g.us.
Include Items Specifies related data to include in the response. Options are: Messages, Notes, Participants. You can select any combination of these.

Output

The output JSON contains detailed information about the specified chat. Depending on the "Include Items" selection, it may include:

  • Messages: An array of message objects exchanged in the chat.
  • Notes: Any notes attached to the chat.
  • Participants: Details about the members of the chat if it is a group.

The structure typically includes chat metadata such as chat ID, timestamps, status, and optionally the included related data arrays.

If binary data were involved (not indicated here), it would represent media files or attachments related to the chat.

Dependencies

  • Requires an active connection to the Wassenger WhatsApp API.
  • Needs an API key credential configured in n8n for authentication.
  • The node depends on internal methods that load available WhatsApp numbers ("devices") dynamically.

Troubleshooting

  • Common Issues:

    • Invalid or missing WhatsApp number ID: Ensure the device ID corresponds to a valid registered WhatsApp number.
    • Incorrect Chat ID format: Verify the chat ID matches the expected pattern for user or group chats.
    • Insufficient permissions or expired API key: Confirm the API key is valid and has access rights to the requested data.
  • Error Messages:

    • Errors returned from the API will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical errors include "Chat not found," "Unauthorized," or "Invalid device ID."
  • Resolution Tips:

    • Double-check input parameters for correctness.
    • Refresh or update the API key credentials.
    • Use the "Include Items" property judiciously to avoid requesting unsupported data combinations.

Links and References

Discussion