WbFbs

Overview

This node interacts with the Wildberries FBS (Fulfillment by Seller) API to update ("patch") specific supply boxes by their identifiers. Specifically, it allows users to modify a box within a supply by adding a list of order IDs to that box. This is useful in scenarios where you need to update the contents of a shipment box after its initial creation, for example, to add additional orders that should be included in the same box.

Practical examples:

• Adding new customer orders to an existing supply box before dispatch.
• Correcting or updating the list of orders assigned to a particular box in a supply.
• Automating supply box updates as part of a fulfillment workflow.

Properties

Output

The node outputs JSON data representing the response from the Wildberries API after patching the supply box. This typically includes confirmation of the updated box details or status information about the patch operation.

If the API supports binary data output (not indicated here), it would represent related files or documents, but based on the provided code and properties, the output is purely JSON.

Dependencies

• Requires access to the Wildberries API endpoint for FBS supplies.
• Needs an API key or authentication token configured in n8n credentials to authorize requests.
• Uses a base URL defined in the bundled Swagger/OpenAPI specification (03-orders-fbs_modified.json).
• Depends on the @devlikeapro/n8n-openapi-node package for building request properties and handling API interaction.

Troubleshooting

• Missing or invalid Supply Id / Trbx Id: Ensure these IDs are correct and exist in the Wildberries system; otherwise, the API will return errors indicating not found or invalid parameters.
• Invalid Order Ids format: The orderIds property must be a valid JSON array. Malformed JSON will cause parsing errors.
• Authentication errors: Verify that the API key or authentication token is correctly set up in n8n credentials and has sufficient permissions.
• API rate limits or downtime: If requests fail repeatedly, check Wildberries API status and consider implementing retry logic or error handling in your workflow.

Common error messages might include:

• "Supply not found" or "Box not found" — verify IDs.
• "Invalid JSON body" — check the formatting of the orderIds.
• "Unauthorized" — check API credentials.

Links and References

• Wildberries FBS API documentation (official site, if available)
• n8n documentation on creating custom nodes and using API credentials
• JSON formatting guides for constructing the orderIds input property