Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node is designed to delete a warehouse from the seller's warehouses by specifying its unique Warehouse Id. It interacts with an external API (likely Wildberries or a similar marketplace) to remove the warehouse record identified by the given ID.
Common scenarios for this node include:
- Managing inventory locations by removing obsolete or closed warehouses.
- Automating cleanup of warehouse data in bulk workflows.
- Integrating with ERP or inventory systems to synchronize warehouse deletions.
Example: A user wants to delete a warehouse with ID 12345 after it has been decommissioned. They provide the Warehouse Id, and the node sends a request to delete that warehouse from the seller's account.
Properties
| Name | Meaning |
|---|---|
| Warehouse Id | The unique identifier (ID) of the seller's warehouse to be deleted. Must be a number. |
Output
The node outputs JSON data representing the response from the API after attempting to delete the specified warehouse. This typically includes confirmation of deletion or error details if the operation failed.
No binary data output is expected.
Dependencies
- Requires an API key credential for authentication with the external service managing the warehouses.
- Depends on the base URL and endpoints defined in the bundled OpenAPI specification.
- Needs proper network access to the external API.
Troubleshooting
- Invalid Warehouse Id: If the provided Warehouse Id does not exist or is incorrect, the API may return an error indicating the warehouse was not found. Verify the Warehouse Id before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or token is correctly configured.
- Network Issues: Connectivity problems can lead to timeouts or unreachable host errors. Check network settings and API availability.
- API Rate Limits: Excessive requests might trigger rate limiting; handle such errors by adding retries or delays.
Links and References
- Refer to the external API documentation for detailed information about warehouse management endpoints.
- n8n documentation on creating and using custom nodes with API integrations.