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 (WB) FBS (Fulfillment by Seller) API to update specific supply orders. The operation "Patch Supplies Orders By Supplyid By Orderid" allows users to modify details of a particular order within a given supply batch by specifying both the supply ID and the order ID.
Typical use cases include:
- Updating the status or details of an order in a supply batch.
- Correcting or amending information related to a specific order without affecting other orders in the same supply.
- Automating supply order management workflows where partial updates are needed.
For example, if you have a supply batch identified by "WB-GI-1234567" and want to update the order with ID 5632423 inside that supply, this node operation facilitates that patch request.
Properties
| Name | Meaning |
|---|---|
| Supply Id | ID of the supply batch to update. Example: "WB-GI-1234567". This identifies the supply containing the order. |
| Order Id | ID of the specific order within the supply to patch. Example: 5632423. |
Output
The node outputs JSON data representing the response from the WB API after attempting to patch the specified order. This typically includes confirmation of the updated fields or the full updated order object as returned by the API.
If the API supports it, the output may also contain error messages or status codes indicating success or failure of the patch operation.
No binary data output is indicated for this node.
Dependencies
- Requires access to the Wildberries API endpoint for FBS orders.
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- Uses a base URL defined in the bundled OpenAPI specification for the WB API.
- Depends on the
@devlikeapro/n8n-openapi-nodepackage for building request properties and handling API interaction.
Troubleshooting
Common issues:
- Invalid or missing Supply Id or Order Id will cause the API to reject the request.
- Authentication failures due to missing or incorrect API credentials.
- Network connectivity problems preventing access to the WB API.
- Attempting to patch an order that does not exist within the specified supply.
Error messages:
- "404 Not Found": The specified supply or order ID does not exist.
- "401 Unauthorized": API credentials are invalid or missing.
- "400 Bad Request": The patch payload is malformed or contains invalid data.
Resolutions:
- Verify that the Supply Id and Order Id are correct and exist in your WB account.
- Ensure API credentials are properly set up in n8n.
- Check network connectivity and API endpoint availability.
- Validate the data being sent in the patch request matches API requirements.
Links and References
- Wildberries FBS API documentation (refer to official WB developer portal)
- n8n documentation on creating custom nodes and using API credentials
- OpenAPI Specification used internally for this node (not publicly linked here)