Actions27
- Account Actions
- Device Actions
- Estatísticas E Log Actions
- Item Actions
- Template Actions
Overview
This node integrates with the etiquetas.io platform to import item data into a specified store. It is designed to facilitate bulk or individual item imports, allowing users to synchronize product information such as pricing, stock levels, barcodes, and custom attributes directly into their store's inventory system.
Common scenarios where this node is beneficial include:
- Migrating product catalogs from external systems into etiquetas.io stores.
- Regularly updating item details like prices, stock quantities, or promotional texts.
- Automating inventory management by importing updated item data from other sources.
For example, a retailer could use this node to import a list of new products with detailed attributes and pricing into their online store, ensuring that all product information is up-to-date and consistent.
Properties
| Name | Meaning |
|---|---|
| storeId | The target store where items will be imported. Can be selected from a searchable list of stores or specified directly by its numeric ID. |
| emptyNeedDelete | Boolean flag indicating whether existing items in the store should be deleted if they are not present in the import data. |
| items | A collection of item attributes to import. Each item can have multiple fields including: attrCategory, attrName, barCode, price, memberPrice, originalPrice, itemTitle, shortTitle, productCode, classLevel, unit, qrCode, productArea, nfcUrl, spec, productSku, stock1, stock2, stock3, promotionText, and up to 50 custom features (custFeature1 through custFeature50). These fields represent detailed product information such as identifiers, pricing, stock levels, descriptions, and customizable metadata. |
Output
The node outputs JSON data representing the result of the import operation. This typically includes confirmation of the imported items, any errors encountered, and status messages from the etiquetas.io API. The output structure reflects the response from the etiquetas.io service after processing the import request.
If binary data is involved (not indicated here), it would generally represent files or media associated with items, but this node focuses on JSON data for item import.
Dependencies
- Requires an API key credential for authenticating with the etiquetas.io platform.
- Needs access to etiquetas.io stores, which can be retrieved via a built-in method to list stores.
- The node depends on etiquetas.io's API endpoints for item import operations.
- Proper configuration of the API authentication token within n8n credentials is necessary.
Troubleshooting
- Invalid Store ID: If the storeId is incorrectly formatted or does not exist, the node may fail. Ensure the store ID is numeric and corresponds to an existing store.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Empty Need Delete Flag Misuse: Setting
emptyNeedDeleteincorrectly might lead to unintended deletion of items. Use caution when enabling this option. - Data Validation Issues: Some item fields expect specific formats (e.g., numeric IDs, strings). Invalid data types or missing required fields may cause errors.
- API Rate Limits or Connectivity: Network issues or rate limiting by etiquetas.io can cause timeouts or errors. Check network connectivity and API usage limits.