Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node operation updates a seller's warehouse information on the Wildberries platform by specifying the warehouse ID. It sends updated details such as the warehouse name and the corresponding Wildberries office ID to modify the existing warehouse record.
Common scenarios for this node include:
- Keeping warehouse data synchronized between internal systems and Wildberries.
- Correcting or updating warehouse names or associated office IDs.
- Automating warehouse management workflows in seller integrations.
For example, if a seller changes the name of their warehouse or reassigns it to a different Wildberries office, this node can be used to update that information programmatically.
Properties
| Name | Meaning |
|---|---|
| Warehouse Id | The unique identifier of the seller's warehouse to update (required). |
| Name | The new or updated name of the seller's warehouse (required). |
| Office Id | The Wildberries office ID associated with the warehouse (required). |
Output
The node outputs JSON data representing the response from the Wildberries API after attempting to update the warehouse. This typically includes confirmation of the update or error details if the operation failed.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses a base URL configured from a bundled OpenAPI specification.
- Proper network access to the Wildberries API endpoint is necessary.
Troubleshooting
- Invalid Warehouse Id: If the provided warehouse ID does not exist, the API may return an error indicating the warehouse was not found. Verify the ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly configured.
- Validation Errors: Providing invalid data types or missing required fields (e.g., empty name) will result in validation errors from the API.
- Network Issues: Connectivity problems can cause request timeouts or failures. Check network settings and API availability.
Links and References
- Wildberries API documentation (official site, if available)
- n8n documentation on creating and using custom nodes
- OpenAPI Specification used for this node (embedded in the source code)