Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node interacts with the Wassenger WhatsApp API to retrieve the status of a specific WhatsApp user by their status ID. It is useful in scenarios where you need to monitor or audit the current state of a user's WhatsApp status message, for example, to check if a status update has been posted or to fetch details about a particular status entry.

A practical example would be an automation that tracks user statuses for customer engagement analysis or compliance monitoring, fetching the status details by providing the WhatsApp number and the unique status ID.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) from which to get the user status. This is selected from available devices.
Status ID The unique identifier of the status to retrieve. It must be a hexadecimal string of length 20-22 or 24 characters.

Output

The node outputs JSON data representing the details of the requested user status. This typically includes information such as the content of the status, timestamps, and any metadata associated with that status entry.

No binary data output is indicated for 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 within n8n.
  • The "WhatsApp Number" property dynamically loads options via a method that fetches available devices linked to the account.

Troubleshooting

  • Common issues:

    • Providing an invalid or incorrectly formatted Status ID may result in errors or no data returned.
    • If the WhatsApp number (device) is not correctly selected or does not exist, the request will fail.
    • Network or authentication failures can occur if the API key is missing, expired, or incorrect.
  • Error messages:

    • Errors related to "status not found" usually indicate the Status ID does not exist or is inaccessible.
    • Authentication errors suggest problems with the API key credential; verify and update it as needed.
    • Rate limiting or connectivity errors require checking network access and API usage limits.

Links and References

Discussion