Overview
This node integrates with Shopware 6, a popular e-commerce platform, to perform various data operations. Specifically, the "Delete Category" operation allows users to delete a category entity from their Shopware store. This is useful for managing product categories by removing obsolete or unwanted categories programmatically within an automation workflow.
Common scenarios include:
- Automatically cleaning up categories that are no longer relevant.
- Managing category lifecycle as part of inventory or catalog updates.
- Integrating with external systems to synchronize category deletions.
Example: A user could set up a workflow that deletes specific categories based on certain triggers, such as when a category becomes empty or after a promotional period ends.
Properties
| Name | Meaning |
|---|---|
| Entity | The type of entity to operate on. Options: category, customer, order, product. For this operation, it should be set to category. |
Note: The provided properties JSON only includes the "Entity" property, which is used to select the target entity type.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of deletion or any relevant metadata returned by the Shopware API about the deleted category.
If the node supports binary data output (not evident from the provided code), it would represent associated files or media related to the entity, but this is not indicated here.
Dependencies
- Requires an active connection to a Shopware 6 instance.
- Needs an API authentication credential configured in n8n to authorize requests to the Shopware API.
- The node dynamically loads operation handlers from local files under an
operationsdirectory, so these must be present and correctly implemented. - Uses Node.js modules
globandpathinternally for file system operations.
Troubleshooting
- Operation Not Found: If the specified operation handler file is missing or misnamed, the node will fail to execute. Ensure the
Delete Categoryoperation file exists under the expected path. - Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- Entity Mismatch: Selecting an entity other than
categorywhile performing the delete category operation may lead to unexpected behavior or errors. - File System Issues: Since the node dynamically imports operation handlers, permission issues or missing files in the
operationsfolder can cause runtime errors.