Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node integrates with the Wassenger WhatsApp API to perform various operations related to WhatsApp messaging and management. Specifically, for the Team resource and the Get Device Team Members operation, it retrieves the list of team members associated with a particular WhatsApp number (device). This is useful in scenarios where you want to manage or audit which users have access to a specific WhatsApp device within your organization.
Practical examples:
- Fetching all team members who can interact with a given WhatsApp number to display in an internal dashboard.
- Auditing user permissions on WhatsApp devices before granting or revoking access.
- Synchronizing team member data from Wassenger into other systems.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) for which to retrieve the associated team members. This is selected from a list of available WhatsApp numbers. |
Output
The node outputs JSON data representing the team members linked to the specified WhatsApp number. Each item in the output array corresponds to a team member's details as returned by the Wassenger API.
If the node supports binary data output in other operations, it would typically represent files or media related to WhatsApp messages, but for this operation, only JSON data about team members is returned.
Dependencies
- Requires an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and the API key having sufficient permissions to query team information.
- The "WhatsApp Number" property dynamically loads available devices via a method named
getDevices, which implies the node fetches device options from the API.
Troubleshooting
Common issues:
- Invalid or expired API key leading to authentication errors.
- Specifying a WhatsApp number that does not exist or is not linked to the account.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from the API will be caught and can appear in the output if "Continue On Fail" is enabled.
- Typical error messages might include "Unauthorized", "Device not found", or "API rate limit exceeded".
Resolutions:
- Verify the API key is correct and has necessary permissions.
- Ensure the WhatsApp number/device ID is valid and active.
- Check network connectivity and retry after some time if rate limits are hit.
Links and References
- Wassenger Official API Documentation (for detailed API capabilities and authentication)
- n8n Documentation on Creating Custom Nodes (for understanding node development concepts)