WassengerInstall

Overview

This node interacts with the Wassenger WhatsApp API to retrieve information about team members. Specifically, the "Get Team Members" operation allows users to fetch a filtered list of users within a team based on various criteria such as user IDs, status, role, device access, and activity timestamps.

Common scenarios where this node is beneficial include:

• Managing and monitoring team members in a WhatsApp-based customer support or sales environment.
• Filtering users by their roles (e.g., Admin, Supervisor, Agent) to assign tasks or analyze team composition.
• Tracking user activity by filtering based on last online or login times.
• Searching for specific users by name or email.
• Paginating through large teams to process or display manageable chunks of data.

Practical example:

• A manager wants to get all active agents who have logged in after a certain date and are assigned to a specific WhatsApp number. They can use this node with filters set for status = Active, role = Agent, loginAfter = [date], and device = [WhatsApp number].

Properties

Output

The output is an array of JSON objects representing team members matching the applied filters. Each object contains details about a user such as their ID, status, role, last online time, last login time, associated devices, and other relevant metadata provided by the Wassenger API.

If the node supports binary data output (not indicated explicitly here), it would typically represent files or media related to users, but for this operation, the output is purely JSON data about team members.

Dependencies

• Requires an API key credential for authenticating with the Wassenger WhatsApp API.
• The node depends on the Wassenger API service being accessible and properly configured.
• Dynamic loading of device options requires connectivity to the API to fetch available WhatsApp numbers/devices.

Troubleshooting

• Common issues:

  • Invalid or missing API key credential will cause authentication failures.
  • Using invalid filter values (e.g., non-existent user IDs or device IDs) may result in empty responses.
  • Pagination parameters out of range might return no results.
  • Network connectivity issues can prevent fetching data from the API.

• Error messages:

  • Authentication errors usually indicate problems with the API key; verify the credential setup.
  • "No users found" or empty results suggest that the filters are too restrictive or incorrect.
  • Rate limiting errors from the API require waiting or adjusting request frequency.

• Resolutions:

  • Ensure the API key credential is correctly configured and has necessary permissions.
  • Double-check filter values and try broader filters to confirm data availability.
  • Handle pagination carefully, especially when iterating over pages.
  • Check network connectivity and API service status.

Links and References

• Wassenger Official API Documentation
• n8n Documentation on Credentials
• Pagination Best Practices