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 Orders). The particular operation "Post Orders Status" allows users to send or update the status of multiple assembly orders by providing their IDs. This can be useful in scenarios where batch updates of order statuses are needed, such as confirming processing stages, updating fulfillment progress, or synchronizing order states between systems.
Practical examples include:
- Sending a list of assembly order IDs to mark them as processed.
- Updating the status of multiple orders after a production step completes.
- Integrating with warehouse management systems to reflect real-time order statuses.
Properties
| Name | Meaning |
|---|---|
| Orders | A JSON array containing the list of assembly order IDs to post status updates for. Example: [5632423] |
Output
The node outputs JSON data reflecting the response from the API after posting the orders' status. The exact structure depends on the API but typically includes confirmation of the updated orders, success indicators, or error messages if any orders failed to update.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the WB API (or equivalent).
- Depends on the base URL and schema defined in the bundled OpenAPI specification (
03-orders-fbs_modified.json). - Uses HTTP headers
Accept: application/jsonandContent-Type: application/json. - No additional external services beyond the specified API are required.
Troubleshooting
- Invalid JSON in Orders property: Since the orders input expects a JSON array, malformed JSON will cause errors. Ensure the input is valid JSON.
- Authentication errors: Missing or invalid API credentials will result in authorization failures. Verify that the API key or token is correctly configured.
- API endpoint issues: If the base URL or endpoint changes, the node may fail. Confirm the API endpoint is reachable and correct.
- Empty or missing orders list: Providing an empty array or no orders may lead to no action or errors. Always supply at least one valid order ID.
Links and References
- WB API Documentation (replace with actual link if available)
- n8n documentation on Creating Custom Nodes
- JSON validation tools for verifying the "Orders" input format