Actions19
- Статистика По Продвижению Actions
- Воронка Продаж Actions
- Поисковые Запросы Actions
- История Остатков Actions
- Аналитика Продавца CSV Actions
Overview
This node interacts with a stock history reporting API to retrieve filtered stock data for various offices. It is designed to post a request that filters stock information based on multiple criteria such as product article numbers, subject IDs, brand names, tag IDs, and stock types within a specified date period. This node is useful in scenarios where users need detailed stock reports filtered by specific product attributes or warehouse types, enabling inventory analysis, stock tracking, and supply chain management.
Practical examples include:
- Generating a report of stock levels for selected products (by article numbers) across marketplace warehouses during a given date range.
- Filtering stock data by brand names or tags to analyze performance or availability.
- Excluding deleted products from the stock report to focus on active inventory.
Properties
| Name | Meaning |
|---|---|
| Nm I Ds | List of WB article numbers (product identifiers) used to filter the stock report. |
| Subject I Ds | List of subject IDs to filter the stock report by specific subjects or categories. |
| Brand Names | List of brand names to filter the stock report by particular brands. |
| Tag I Ds | List of tag IDs to filter the stock report by assigned tags. |
| Current Period | The date range for the stock report, defined by a start and end date (e.g., {"start": "YYYY-MM-DD", "end": "YYYY-MM-DD"}). |
| Stock Type | Type of stock warehouses to include: all (""), WB warehouses ("wb"), or Marketplace warehouses ("mp"). |
| Skip Deleted Nm | Boolean flag indicating whether to exclude deleted products from the report (true to hide). |
Output
The node outputs JSON data containing the filtered stock report results for the specified offices and criteria. The exact structure depends on the API response but typically includes stock quantities, product details, and possibly metadata about the warehouses or periods.
If binary data were involved (not indicated here), it would represent files or attachments related to the stock report, but this node focuses on JSON responses.
Dependencies
- Requires an API key credential for authentication with the external stock reporting service.
- Depends on the base URL and endpoint configuration provided by the bundled swagger/openapi specification.
- Uses JSON parsing for input properties to correctly format the request body.
Troubleshooting
- Invalid JSON Input: If the JSON arrays or objects provided in properties like Nm I Ds or Current Period are malformed, the node will fail to parse them. Ensure valid JSON syntax.
- Missing Required Fields: Properties marked as required (Current Period, Stock Type, Skip Deleted Nm) must be provided; otherwise, the request may be rejected.
- API Authentication Errors: If the API key or credentials are missing or invalid, the node will return authentication errors. Verify the configured credentials.
- Empty or No Data Returned: If filters are too restrictive or incorrect, the API might return empty results. Adjust filter values accordingly.
- Date Format Issues: The Current Period dates must follow the expected format (YYYY-MM-DD); otherwise, the API may reject the request.
Links and References
- WB API Documentation (example placeholder, replace with actual API docs)
- n8n Documentation on Creating Custom Nodes
- JSON Syntax Guide: https://www.json.org/json-en.html