Actions27
- Account Actions
- Device Actions
- Estatísticas E Log Actions
- Item Actions
- Template Actions
Overview
This node integrates with the etiquetas.io platform, specifically providing access to various resources including statistics and logs. The "Estatisticas De Modelos De Etiquetas" operation under the "Estatísticas E Log" resource fetches statistical data related to label models for a specified store.
Typical use cases include:
- Retrieving usage or performance statistics of label models in a retail environment.
- Monitoring label printing or scanning activities associated with specific stores.
- Analyzing label model metrics to optimize inventory or operational workflows.
For example, a user might select a particular store by its ID and obtain detailed statistics about how different label models are performing or being utilized in that store.
Properties
| Name | Meaning |
|---|---|
| storeId | Identifier of the store for which to retrieve label model statistics. Can be selected from a searchable list of stores or entered directly as an ID (numeric only). |
Output
The node outputs JSON data containing the statistics of label models for the specified store. The exact structure depends on the etiquetas.io API response but generally includes metrics and details relevant to label model usage.
No binary data output is indicated in the provided code.
Dependencies
- Requires an API key credential for etiquetas.io to authenticate requests.
- Uses an internal method to fetch the list of stores for selection (
getStores). - Relies on the etiquetas.io API endpoints corresponding to statistics retrieval.
Troubleshooting
- Invalid Store ID: If the store ID does not match the expected numeric format, the node will likely reject it due to regex validation. Ensure the store ID contains only digits.
- Authentication Errors: Missing or invalid API credentials will prevent successful API calls. Verify that the API key credential is correctly configured.
- Store Not Found: Selecting a store from the list ensures validity; manually entered IDs must correspond to existing stores.
- API Rate Limits or Downtime: Network issues or API limits may cause errors; check connectivity and API status.