WbDbs

Overview

This node interacts with the Wildberries DBS (Drop-Shipping Business System) API to update the status of assembly orders by rejecting them based on a specific order ID. It is useful in scenarios where an order needs to be programmatically rejected, for example, due to stock issues, customer cancellation, or other business rules that require marking an order as rejected within the DBS system.

A practical example would be automating the rejection of orders that fail quality checks or cannot be fulfilled, ensuring the order status is updated promptly without manual intervention.

Properties

Output

The node outputs JSON data representing the response from the Wildberries DBS API after attempting to reject the specified order. This typically includes confirmation of the rejection status or error details if the operation failed.

No binary data output is indicated.

Dependencies

• Requires an API key credential for authenticating requests to the Wildberries API.
• The node uses a base URL derived from an OpenAPI specification bundled internally.
• Proper configuration of the API authentication credentials in n8n is necessary for successful execution.

Troubleshooting

• Common Issues:

  • Invalid or missing Order Id: Ensure the Order Id provided exists and is correct.
  • Incorrect or missing confirmation Code: The code must be valid and properly formatted.
  • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Network or API downtime: Check connectivity and Wildberries API status.

• Error Messages:

  • Authorization failures usually indicate invalid or expired API credentials.
  • Validation errors may occur if required properties are missing or malformed.
  • API rate limits might cause temporary blocking; handle retries accordingly.

Links and References

• Wildberries DBS API documentation (refer to official Wildberries developer resources)
• n8n documentation on creating and using custom nodes with API integrations