Actions34
- Сборочные Задания Actions
- Метаданные Actions
- Поставки FBS Actions
- Post Supplies
- Get Supplies
- Patch Supplies Orders By Supplyid By Orderid
- Get Supplies By Supplyid
- Delete Supplies By Supplyid
- Get Supplies Orders By Supplyid
- Patch Supplies Deliver By Supplyid
- Get Supplies Barcode By Supplyid
- Get Supplies Trbx By Supplyid
- Post Supplies Trbx By Supplyid
- Delete Supplies Trbx By Supplyid
- Patch Supplies Trbx By Supplyid By Trbxid
- Delete Supplies Trbx Orders By Supplyid By Trbxid By Orderid
- Post Supplies Trbx Stickers By Supplyid
- Пропуска Actions
- Доставка Курьером WB DBW Actions
Overview
This node interacts with a specific API to update metadata related to orders, specifically setting the GTIN (Global Trade Item Number) for an order identified by its Order Id. It is useful in scenarios where you need to enrich or correct product metadata associated with orders in a system, such as updating barcodes or product identifiers after order creation.
A practical example would be integrating this node into an automation workflow that processes order data and ensures each order has accurate GTIN information for inventory tracking or compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly task or order for which the GTIN will be set. |
| Gtin | The Global Trade Item Number (GTIN) value to assign to the specified order. |
Output
The node outputs JSON data representing the response from the API after attempting to update the GTIN for the given order. This typically includes confirmation of success or details about the updated order metadata.
If the node supports binary data output, it would generally relate to any file or media returned by the API, but based on the provided code and properties, the primary output is JSON.
Dependencies
- Requires access to an external API endpoint related to order metadata management.
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- The base URL and request defaults are derived from a bundled OpenAPI specification, ensuring consistent API interaction.
Troubleshooting
Common issues:
- Invalid or missing Order Id or GTIN values can cause the API to reject the request.
- Authentication failures if the API key or token is not properly configured.
- Network connectivity problems preventing communication with the API endpoint.
Error messages:
- Errors indicating "Unauthorized" suggest checking API credentials.
- Validation errors about the Order Id or GTIN imply verifying input correctness.
- Timeout or connection errors require network troubleshooting or API availability checks.
Links and References
- GTIN Information
- Documentation for the external API should be consulted for detailed request/response formats and error codes (not included in the source).