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 interacts with the Wassenger WhatsApp API to perform various operations related to WhatsApp messaging and management. Specifically, for the Labels resource with the Get Labels operation, it retrieves labels associated with a specified WhatsApp number (device). This is useful for organizing and categorizing chats or contacts within WhatsApp through labels.
Practical scenarios include:
- Fetching all labels assigned to a particular WhatsApp number to display or process them in workflows.
- Automating label-based filtering or routing of messages.
- Integrating label data into CRM or support systems for better contact management.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The ID of the WhatsApp number (device) for which to retrieve labels. This must be selected from available devices loaded dynamically. |
Output
The node outputs an array of JSON objects representing the labels retrieved for the specified WhatsApp number. Each object typically contains label details such as label name, ID, and possibly metadata depending on the API response.
If the node supports binary data output (not indicated here), it would represent any files or media related to labels, but for this operation, the output is purely JSON.
Example output structure (conceptual):
[
{
"id": "label_123",
"name": "Support",
"color": "#FF0000"
},
{
"id": "label_456",
"name": "Sales",
"color": "#00FF00"
}
]
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.
- The "WhatsApp number" property relies on dynamic loading of available devices via a method named
getDevices.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Specifying a WhatsApp number that does not exist or is not linked to the account will result in errors or empty results.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors: Check that the API key credential is correctly set up and valid.
- "Device not found" or similar: Verify the WhatsApp number ID is correct and available.
- API rate limits or service downtime: Retry after some time or check Wassenger service status.
Links and References
- Wassenger Official API Documentation (for detailed API capabilities and label management)
- n8n documentation on Creating Custom Nodes