Actions19
- Agent Actions
- Campaign Actions
- Contact Actions
- Custom Field Actions
- Label Actions
- WhatsApp Actions
Overview
This node integrates with the Wasapi API, specifically providing functionality to retrieve a label by its ID. It is useful in scenarios where you need to fetch detailed information about a specific label within the Wasapi system, such as for organizing or filtering messages, contacts, or other entities associated with labels.
A practical example would be automating workflows that require fetching label details to apply conditional logic based on label properties or to synchronize label data with other systems.
Properties
| Name | Meaning |
|---|---|
| Label ID | ID of the label to retrieve |
The "Label ID" property is required and expects a string representing the unique identifier of the label you want to get from the Wasapi API.
Output
The node outputs JSON data containing the details of the requested label. This typically includes all relevant fields returned by the Wasapi API for a label entity, such as its name, ID, description, and any metadata associated with it.
If the node supports binary data output (not indicated here), it would represent any file or media content related to the label, but this is not applicable for the "Get By ID" label operation.
Dependencies
- Requires an active connection to the Wasapi API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://api-ws.wasapi.io/api/v1.
Troubleshooting
Common issues:
- Invalid or missing Label ID: Ensure the Label ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key or token is valid and has sufficient permissions.
- Network or connectivity problems: Check internet access and API endpoint availability.
Error messages:
"Resource "labels" with operation "getById" is not supported": This indicates the node configuration might be incorrect or the operation is not implemented; verify resource and operation names.- API response errors like 404 Not Found usually mean the Label ID does not exist.
- 401 Unauthorized errors suggest issues with API credentials.
Resolving these typically involves verifying input parameters, checking credential validity, and ensuring the Wasapi service is operational.
Links and References
- Wasapi Official API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general guidance on using custom nodes and credentials)