Actions27
- Account Actions
- Device Actions
- Estatísticas E Log Actions
- Item Actions
- Template Actions
Overview
This node integrates with the etiquetas.io platform, focusing on managing and retrieving data related to smart labels (etiquetas). Specifically, the "Consulta Status De Etiquetas" operation under the "Estatísticas E Log" resource allows users to query the status of labels associated with a particular store. This is useful for scenarios where businesses want to monitor label statuses in real-time or gather statistics for inventory management, logistics, or retail analytics.
Practical examples include:
- Checking if labels are active or inactive in a specific store.
- Monitoring label usage or errors across different store locations.
- Integrating label status data into broader business intelligence workflows.
Properties
| Name | Meaning |
|---|---|
| storeId | Identifier of the store to query label status for. Can be selected from a list of stores or entered manually by ID (numeric only). |
Output
The node outputs JSON data representing the status information of labels for the specified store. The exact structure depends on the etiquetas.io API response but typically includes details such as label identifiers, their current status, timestamps, and possibly error or usage logs.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for etiquetas.io to authenticate requests.
- Uses an internal method to fetch available stores for selection (
getStores), which implies connectivity to etiquetas.io's store listing endpoint. - The node relies on the etiquetas.io API endpoints corresponding to statistics and logs.
Troubleshooting
- Invalid Store ID: If the store ID does not match the expected numeric format, the node will reject it due to regex validation. Ensure the store ID contains only digits.
- Authentication Errors: Missing or invalid API credentials will prevent successful queries. Verify that the API key is correctly configured.
- Store Not Found: Selecting a store that does not exist or has no associated labels may result in empty or error responses.
- Network Issues: Connectivity problems with the etiquetas.io API can cause timeouts or failures; check network settings and API availability.