etiquetas.io icon

etiquetas.io

etiquetas.io

Overview

This node integrates with the etiquetas.io platform, providing various operations related to accounts, items, devices, templates, authentication, and statistics. Specifically, for the Account resource and the Listar Lojas (List Stores) operation, it retrieves a list of stores associated with the user's account on etiquetas.io.

Common scenarios where this node is beneficial include:

  • Fetching all stores linked to an account for inventory or label management.
  • Synchronizing store data from etiquetas.io into other systems.
  • Displaying available stores for selection in workflows that manage labels or devices per store.

Example use case: A user wants to automate label printing by first retrieving their list of stores, then processing label templates for each store dynamically.

Properties

Name Meaning
storeName Optional string to filter the list of stores by name. If provided, only matching stores are returned.

Output

The node outputs JSON data representing the list of stores retrieved from etiquetas.io. Each item in the output corresponds to a store object containing details such as store identifiers, names, and possibly other metadata relevant to the store.

If binary data is involved (not indicated explicitly here), it would typically represent files or label templates, but for this operation, the output is purely JSON.

Dependencies

  • Requires an API key credential for etiquetas.io to authenticate requests.
  • The node depends on internal helper functions and resources bundled within the node's codebase to perform API calls and process responses.
  • No external environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an incorrect or misspelled storeName filter may result in empty results.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Authentication errors typically indicate invalid API keys; verify and update credentials.
    • Empty response or no stores found might mean the account has no stores or the filter does not match any store.
    • Timeout or network errors suggest checking internet connection or API service status.

Links and References

Discussion