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) API, specifically targeting the "Доставка Курьером WB DBW" resource to update or confirm orders by their Order ID. The operation "Patch Orders Confirm By Orderid" allows users to send a patch request to confirm or modify the status of an existing order identified by its unique Order ID.
Typical use cases include:
- Updating the confirmation status of a courier delivery order in Wildberries.
- Automating order management workflows where order statuses need to be programmatically confirmed or patched.
- Integrating Wildberries order updates into broader logistics or fulfillment systems.
For example, after a courier completes a delivery, this node can be used to confirm the order status automatically in the WB system.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly task/order to be patched or confirmed. This is a required numeric field. |
Output
The node outputs JSON data representing the response from the WB API after attempting to patch/confirm the order. This typically includes confirmation details or status updates related to the specified order.
No binary data output is indicated in the source code.
Dependencies
- Requires access to the Wildberries API.
- Needs an API key credential for authentication with the WB API (referred generically as "an API key credential").
- The base URL and endpoint definitions are derived from a Swagger/OpenAPI specification bundled within the node.
- The node uses HTTP headers specifying
Accept: application/jsonandContent-Type: application/json.
Troubleshooting
Common issues:
- Invalid or missing Order Id: The node requires a valid numeric Order Id; providing an incorrect or missing value will cause errors.
- Authentication failures: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Connectivity issues or WB API outages may result in failed requests.
Error messages:
- Errors related to invalid input parameters usually indicate problems with the Order Id.
- Authorization errors suggest issues with the provided API credentials.
- Unexpected API responses might require checking the WB API documentation or verifying the node's configuration.
Links and References
- Wildberries API Documentation (general reference): https://openapi.wildberries.ru/
- n8n OpenAPI Node integration guide: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-openapi-node/