WbFbs

Overview

This node interacts with the Wildberries (WB) API, specifically targeting the "Доставка Курьером WB DBW" resource to update ("patch") assemble orders by their order ID. It is designed to modify existing assemble orders in the WB delivery system by sending partial updates based on the provided order identifier.

Common scenarios for this node include:

• Updating the status or details of an assemble order after changes in the courier delivery process.
• Correcting or amending information related to a specific assemble order without replacing the entire order data.
• Automating order management workflows where only certain fields need to be patched rather than fully replaced.

For example, if a logistics team needs to update the assemble order's status or add notes to an existing order identified by its Order Id, this node facilitates that operation efficiently.

Properties

Output

The node outputs JSON data representing the response from the WB API after attempting to patch the specified assemble order. This typically includes confirmation of the update, any changed fields, or error messages if the operation failed.

No binary data output is indicated in the source code.

Dependencies

• Requires access to the Wildberries API.
• Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
• Uses a base URL and request defaults derived from a Swagger/OpenAPI specification bundled within the node.
• Depends on the @devlikeapro/n8n-openapi-node package for building properties and handling requests.

Troubleshooting

• Missing or invalid Order Id: Since the Order Id is required, omitting it or providing an invalid number will cause errors. Ensure the Order Id corresponds to an existing assemble order.
• Authentication errors: If the API key or token is missing or incorrect, the node will fail to authenticate with the WB API.
• API endpoint changes: If the WB API changes its endpoints or request schema, the node may fail unless updated accordingly.
• Network issues: Connectivity problems can cause timeouts or failures when contacting the WB API.

Common error messages might include HTTP 4xx or 5xx responses indicating client or server errors. Checking the API credentials, network connectivity, and validity of the Order Id usually resolves these issues.

Links and References

• Wildberries API documentation (refer to official WB developer resources)
• n8n documentation on creating custom nodes and using API credentials
• Swagger/OpenAPI specifications for WB API (embedded in the node source)