WbDbs icon

WbDbs

n8n node to interact with WB API

Actions16

Overview

This node interacts with the Wildberries (WB) API to retrieve assembly orders data from the DBS (Dropshipping Business System). Specifically, the "Get Dbs Orders" operation fetches a paginated list of DBS orders within a specified date range. This is useful for automating order management workflows, such as syncing orders into an ERP system, monitoring order statuses, or generating reports on assembly tasks.

Practical examples:

  • Automatically retrieving all DBS orders created between two dates for further processing.
  • Paginating through large sets of orders by using the Next parameter to fetch subsequent batches.
  • Limiting the number of orders fetched per request to optimize performance and avoid rate limits.

Properties

Name Meaning
Limit Pagination parameter that sets the maximum number of orders to return in one request.
Next Pagination parameter indicating the starting point for the next batch of data. For the first call, set to 0; for subsequent calls, use the value returned in the response's next field.
Date From Start date of the period to fetch orders for, expressed as a Unix timestamp (seconds since epoch).
Date To End date of the period to fetch orders for, expressed as a Unix timestamp.

Output

The node outputs JSON data representing the retrieved DBS orders. The structure typically includes:

  • An array of order objects containing details about each assembly order.
  • A next field indicating the offset or token to be used for fetching the next page of results.

If binary data were involved (e.g., files or attachments), it would be summarized here, but this node focuses on JSON order data only.

Dependencies

  • Requires access to the Wildberries API, which implies the need for an API key or authentication token configured in n8n credentials.
  • The node uses a base URL derived from an OpenAPI specification bundled internally.
  • No additional external dependencies beyond standard HTTP requests and the WB API.

Troubleshooting

  • Common issues:
    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid timestamps or date ranges may result in empty responses or errors.
    • Pagination parameters (Limit and Next) must be managed carefully to avoid missing data or infinite loops.
  • Error messages:
    • Authentication errors usually indicate misconfigured or expired API keys.
    • Validation errors may occur if required parameters are missing or out of expected range.
    • Network or timeout errors suggest connectivity issues with the WB API endpoint.

To resolve these:

  • Verify API credentials and permissions.
  • Ensure timestamps are valid Unix timestamps and that Date From is before Date To.
  • Use the next value from the response to paginate correctly.
  • Check network connectivity and retry failed requests.

Links and References

Discussion