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 by associating an array of marking codes (Sgtins) with a given order ID. It is useful in scenarios where you need to programmatically attach or update serialized product codes or tracking identifiers to an existing assembly or production order. For example, this can be used in supply chain management or inventory systems to ensure that each order has the correct set of serialized codes for traceability.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly or production order to which the marking codes will be attached. Must be provided as a number. |
| Sgtins | A JSON array of marking codes (serialized GTINs). Each code must be between 16 and 135 characters long. These codes represent product serialization or tracking identifiers associated with the order. |
Output
The node outputs JSON data reflecting the result of the update operation. This typically includes confirmation of the updated order metadata or any response returned by the API after attaching the Sgtins to the specified order. There is no indication of binary data output.
Dependencies
- Requires an API key credential for authentication with the external service managing order metadata.
- The node uses a base URL configured from an OpenAPI specification bundled within its dependencies.
- Proper network access to the external API endpoint is necessary.
Troubleshooting
- Invalid Order Id: If the order ID does not exist or is invalid, the API may return an error indicating the order was not found. Verify the order ID before running the node.
- Malformed Sgtins JSON: The Sgtins property expects a valid JSON array of strings. Errors parsing this input will cause the request to fail. Ensure the JSON is correctly formatted.
- Authentication Errors: Missing or incorrect API credentials will lead to authorization failures. Confirm that the API key or token is correctly configured in n8n.
- Code Length Violations: Each Sgtin must be between 16 and 135 characters. Codes outside this range may cause validation errors.
- Network Issues: Connectivity problems to the API endpoint will prevent successful execution.
Links and References
- No direct external links are provided in the source code. Users should refer to the documentation of the external API managing order metadata and serialized codes for detailed information on request formats and responses.