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 the Wildberries API to post status history updates for assembly orders (Сборочные Задания). It is useful in scenarios where you need to update or track the status changes of multiple assembly orders programmatically within an automation workflow. For example, after processing or shipping certain orders, you can use this node to send their updated statuses back to the Wildberries system.
Properties
| Name | Meaning |
|---|---|
| Orders | IDs of the assembly orders to update. This property accepts a JSON array of order IDs, e.g., [123456789, 987654321]. |
Output
The node outputs JSON data representing the response from the Wildberries API after posting the status history for the specified orders. The exact structure depends on the API response but typically includes confirmation of the update or error details if the operation failed.
No binary data output is indicated.
Dependencies
- Requires access to the Wildberries API.
- Needs an API key credential configured in n8n for authentication with the Wildberries service.
- The node uses a base URL and OpenAPI specification bundled internally to construct requests.
Troubleshooting
- Invalid Order IDs: If the provided order IDs are incorrect or do not exist, the API may return errors. Verify that the order IDs are valid and correctly formatted as a JSON array.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is properly set up in n8n.
- Network Issues: Connectivity problems can prevent successful API calls. Check network settings and Wildberries API availability.
- Malformed JSON Input: The "Orders" property expects a valid JSON array. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
Links and References
- Wildberries API Documentation (general reference for the API endpoints)
- n8n documentation on creating custom nodes