Actions16
- Сборочные Задания DBS Actions
- Метаданные DBS Actions
Overview
This node interacts with the Wildberries (WB) API to retrieve metadata related to DBS (Dropshipping by Seller) orders. Specifically, the operation "Get Dbs Orders Meta By Orderid" fetches detailed metadata for a given assembly order identified by its unique Order Id. This is useful in scenarios where you need to programmatically access order details for processing, reporting, or integration with other systems.
Practical examples include:
- Automatically fetching order metadata after an order is placed to update internal databases.
- Integrating order metadata retrieval into workflows that handle shipping, invoicing, or customer notifications.
- Auditing or analyzing order data for business intelligence purposes.
Properties
| Name | Meaning |
|---|---|
| Order Id | The unique identifier of the assembly order to retrieve metadata for. Must be a number. |
Output
The node outputs JSON data containing the metadata of the specified DBS order. The exact structure depends on the WB API response schema but typically includes fields such as order details, status, items, timestamps, and other relevant metadata.
If the node supports binary data output, it would represent associated files or documents related to the order, but based on the provided code and operation, the output is primarily JSON metadata.
Dependencies
- Requires access to the Wildberries API.
- Needs an API key credential or similar authentication token configured in n8n to authorize requests.
- Depends on the base URL and OpenAPI specification defined in the bundled swagger JSON file (
04-orders-dbs_modified.json). - Uses an external library for building properties and handling API requests (
@devlikeapro/n8n-openapi-node).
Troubleshooting
Common issues:
- Invalid or missing Order Id: Ensure the Order Id is provided and is a valid number.
- Authentication errors: Verify that the API key or credentials are correctly set up in n8n.
- Network or API endpoint errors: Check connectivity and that the base URL is correct.
- Unexpected API responses: Confirm that the WB API has not changed and matches the swagger definition used.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials.
- "Order not found" or similar: Verify the Order Id exists and is correct.
- "Request timeout" or "Network error": Inspect network settings and API availability.
Links and References
- Wildberries API Documentation (general reference)
- n8n documentation on creating custom nodes
- Swagger/OpenAPI specification format: https://swagger.io/specification/
Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic imports.