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 by associating an IMEI number with a given order ID. It is designed for scenarios where you need to link or update the IMEI information of a device or product within an order management system. For example, in logistics or assembly workflows, this node can be used to ensure that each assembled order has its corresponding IMEI recorded accurately.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly order (ID сборочного задания). Must be a number. |
| Imei | The IMEI number to associate with the order. Must be a string representing the device's IMEI. |
Output
The node outputs JSON data reflecting the result of the operation, typically confirming the successful association of the IMEI with the specified order ID. The exact structure depends on the API response but generally includes status and any relevant metadata confirmation.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external WB API service.
- The node uses a base URL and request defaults configured from an OpenAPI specification bundled internally.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Order Id or IMEI values will cause the API call to fail.
- Authentication errors if the API key credential is not set or invalid.
- Network or connectivity issues when reaching the external API endpoint.
Error messages:
- Errors related to missing required parameters ("Order Id" or "Imei") should be resolved by providing valid inputs.
- Authentication failures require checking the API key credential configuration.
- API response errors may include HTTP status codes indicating issues such as unauthorized access, bad requests, or server errors; reviewing the API documentation and logs can help resolve these.
Links and References
- WB API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes