WassengerInstall

Overview

This node integrates with the Wassenger WhatsApp API to manage queued WhatsApp messages. Specifically, the "Route Queue" operation under the "Queue" resource allows users to reroute queued messages from one WhatsApp number (device) to another target WhatsApp number (device). This is useful in scenarios where message handling needs to be dynamically redirected, such as transferring message queues between different agents or devices for load balancing or operational reasons.

Practical examples include:

• Redirecting all pending messages from a temporarily unavailable WhatsApp number to an active one.
• Managing message queues across multiple WhatsApp numbers in a customer support environment to optimize response times.

Properties

Both properties require selecting from available WhatsApp devices loaded dynamically via the node's method.

Output

The node outputs JSON data representing the result of the rerouting operation. Typically, this includes confirmation details about the queue routing action performed by the API. The exact structure depends on the API response but generally confirms success or failure and may include metadata about the affected queue.

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.
• Dynamic loading of WhatsApp device options requires connectivity to the Wassenger API to fetch available devices.

Troubleshooting

• Common Issues:

  • Invalid or missing WhatsApp device IDs can cause failures in rerouting.
  • Network or authentication errors with the Wassenger API may prevent successful execution.
  • Selecting the same device for both source and target might lead to no effective change or errors.

• Error Messages:

  • Errors related to invalid device IDs typically indicate that the selected WhatsApp number does not exist or is not accessible.
  • Authentication errors suggest issues with the provided API key credential; verify the key and permissions.
  • API rate limits or service downtime may cause temporary failures; retry after some time.

To resolve these issues, ensure correct device IDs are selected, verify API credentials, and check network connectivity.

Links and References

• Wassenger Official API Documentation
• n8n Documentation on Custom Nodes