Actions115
- Course Actions
- Bundle Actions
- Course Grade Actions
- Course Grade Detail Actions
- Course Teacher Actions
- Email Actions
- Email Campaign Actions
- Email Campaign Course Actions
- Email Campaign Excluded Course Actions
- Email Campaign Excluded List Actions
- Enroll Actions
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
The "Remove Product" operation under the "Bundle" resource in this Mindz node allows users to remove a specific product from an existing bundle. This is useful when managing collections of products grouped as bundles, enabling dynamic updates to the bundle contents without recreating the entire bundle.
Practical scenarios include:
- E-commerce platforms where product bundles are offered and need to be updated by removing discontinued or out-of-stock products.
- Subscription services that package multiple items together and want to adjust offerings based on availability or customer preferences.
- Digital content providers managing course or media bundles, needing to remove certain products from a bundle dynamically.
Properties
| Name | Meaning |
|---|---|
| Bundle ID | The unique identifier of the bundle from which a product will be removed. |
| Product ID | The unique identifier of the product to be removed from the specified bundle. |
Output
The output JSON structure typically contains the response from the Mindz API after attempting to remove the product from the bundle. This may include confirmation of removal, updated bundle details, or error information if the operation failed.
If the node supports binary data output (not indicated here), it would represent any file or media data returned by the API, but for this operation, the output is expected to be purely JSON-based.
Dependencies
- Requires an active connection to the Mindz API using an OAuth2-based API key credential.
- The node depends on the Mindz API endpoints related to bundle management.
- Proper configuration of the Mindz OAuth2 credentials within n8n is necessary for authentication.
Troubleshooting
Common Issues:
- Invalid or missing Bundle ID or Product ID parameters can cause the operation to fail.
- Insufficient permissions or expired API tokens may result in authorization errors.
- Attempting to remove a product that does not exist in the specified bundle might return an error or no-op response.
Error Messages:
- "Bundle not found": Verify the Bundle ID is correct and exists.
- "Product not found in bundle": Confirm the Product ID is part of the specified bundle.
- "Unauthorized" or "Authentication failed": Check that the API credentials are valid and have not expired.
Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring the user has appropriate access rights.
Links and References
- Mindz API Documentation (hypothetical link as actual URL is not provided)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- General n8n Node Development: https://docs.n8n.io/integrations/creating-nodes/