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 is designed to interact with a specific API related to "Сборочные Задания" (Assembly Tasks). The particular operation "Post Files Orders External Stickers" allows users to post or send external sticker files associated with assembly task orders. This can be useful in scenarios where you need to upload or link sticker files to multiple assembly orders for processing, tracking, or printing purposes.
Practical examples include:
- Sending sticker files to an external system for labeling assembly orders.
- Automating the process of attaching stickers to multiple assembly tasks in bulk.
- Integrating with warehouse or logistics systems that require sticker data for order fulfillment.
Properties
| Name | Meaning |
|---|---|
| Orders | An array of assembly task order IDs. These are the identifiers of the assembly tasks for which external sticker files will be posted. |
The property expects a JSON array of numeric IDs representing the assembly orders.
Output
The node outputs JSON data corresponding to the response from the API after posting the external sticker files for the specified orders. The exact structure depends on the API but typically includes confirmation of success, error messages if any, and possibly metadata about the processed orders.
If binary data is involved (e.g., actual sticker files), it would be handled accordingly, but based on the provided code and properties, the main output is JSON.
Dependencies
- Requires access to the WB API (a third-party or internal API related to assembly orders).
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- Uses a base URL defined in the node's configuration, likely pointing to the WB API endpoint.
- Depends on the
@devlikeapro/n8n-openapi-nodepackage for building request properties and handling OpenAPI specifications.
Troubleshooting
Common Issues:
- Invalid or missing order IDs in the "Orders" property may cause the API to reject the request.
- Authentication failures if the API key or token is not set up correctly.
- Network issues or incorrect base URL configuration can prevent successful API calls.
Error Messages:
- Errors indicating invalid JSON input for the "Orders" property suggest malformed JSON; ensure the array is properly formatted.
- Authorization errors imply missing or incorrect API credentials; verify credential setup.
- API response errors might indicate issues with the orders themselves (e.g., non-existent order IDs).
To resolve these, double-check the input JSON format, confirm API credentials, and validate order IDs before execution.
Links and References
- No direct links available from the source code.
- For more information, consult the WB API documentation related to assembly orders and external stickers.
- Refer to n8n documentation on how to configure API credentials and use JSON input properties.