WbFbs icon

WbFbs

n8n node to interact with WB API

Overview

This node interacts with the Wildberries (WB) API to retrieve barcode stickers for FBS (Fulfillment by Seller) supplies based on a given supply ID. It is useful in scenarios where sellers or warehouse managers need to generate or obtain barcode labels for shipments they are preparing or have prepared for fulfillment centers. For example, a seller can use this node to automatically fetch barcode images or print-ready label formats for their supply shipments, streamlining logistics and inventory management.

Properties

Name Meaning
Supply Id The unique identifier of the supply shipment for which the barcode sticker is requested.
Type The format/type of the barcode sticker to retrieve. Options: svg, zplv, zplh, png.
  • Supply Id is a required string input representing the supply's ID.
  • Type is a required option input specifying the desired output format of the barcode sticker:
    • svg — Scalable Vector Graphics format.
    • zplv — Zebra Programming Language vertical format.
    • zplh — Zebra Programming Language horizontal format.
    • png — Portable Network Graphics raster image.

Output

The node outputs JSON data containing the barcode sticker corresponding to the specified supply ID and type. The exact structure depends on the API response but generally includes the barcode image or label data encoded in the requested format.

If the selected type corresponds to an image format (svg or png), the output will contain the image data encoded as a string (likely base64 or raw SVG content). For ZPL formats (zplv or zplh), the output contains printer-ready label commands as text.

No binary data output is explicitly indicated, so all data is expected in JSON fields.

Dependencies

  • Requires access to the Wildberries API with appropriate authentication credentials (an API key or token).
  • The node expects the WB API base URL and endpoints configured internally via bundled swagger/openAPI definitions.
  • No additional external dependencies beyond standard HTTP request capabilities and the WB API credential.

Troubleshooting

  • Invalid Supply Id: If the supply ID does not exist or is malformed, the API may return an error or empty result. Verify the supply ID correctness.
  • Unsupported Type: Selecting a type not supported by the API or misspelling the type option could cause errors.
  • Authentication Errors: Missing or invalid API credentials will prevent successful requests.
  • Network Issues: Connectivity problems to the WB API endpoint will cause failures.
  • Response Parsing: Unexpected API responses or changes in the API schema might lead to parsing errors.

To resolve these issues:

  • Double-check supply IDs and type options.
  • Ensure valid API credentials are configured in n8n.
  • Test network connectivity.
  • Review API documentation for any updates or changes.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion