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 node provides integration with the Mindz API, allowing users to manage various Mindz resources such as bundles, courses, users, teams, subscriptions, emails, and payment-related entities. Specifically, for the Bundle resource with the Delete operation, this node enables users to delete a specific bundle by its identifier.
This functionality is useful in scenarios where you need to programmatically remove bundles from your Mindz account, for example:
- Cleaning up outdated or deprecated bundles.
- Automating bundle lifecycle management in workflows.
- Integrating Mindz bundle deletion into larger automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Bundle ID | The unique identifier of the bundle to delete. This is a required string input property. |
Output
The node outputs JSON data representing the result of the delete operation on the specified bundle. Typically, this output will confirm whether the deletion was successful or provide details about the deleted bundle. The exact structure depends on the Mindz API response but generally includes status information.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential.
- The node depends on the Mindz API being accessible and the provided credentials having sufficient permissions to delete bundles.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Bundle ID will likely cause the API to return an error indicating that the bundle could not be found.
- Insufficient permissions or expired credentials may result in authentication errors.
- Network connectivity problems can prevent communication with the Mindz API.
Error messages and resolutions:
- "Bundle not found": Verify the Bundle ID is correct and exists in your Mindz account.
- "Unauthorized" or "Authentication failed": Check that the API credentials are valid and have the necessary scopes.
- Timeout or network errors: Ensure stable internet connection and that the Mindz API endpoint is reachable.
Links and References
- Mindz API Documentation (general reference for API endpoints and operations)
- OAuth2 Authentication setup guides for API access
(Note: Specific URLs are not included due to lack of explicit references in the source code.)