Mindz icon

Mindz

Interact with Mindz API

Actions116

Overview

The Mindz node integrates with the Mindz API to manage various resources such as bundles, courses, users, teams, subscriptions, emails, and payments. Specifically, for the Bundle resource with the Delete operation, this node allows users to delete an existing bundle by specifying its unique identifier.

This operation is useful in scenarios where you need to programmatically remove a bundle 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. Typically, this will include confirmation that the bundle was successfully deleted or details about any error encountered.

If the node supports binary data output (not indicated here), it would typically relate to file attachments or media associated with the bundle, but this is not applicable for the delete operation.

Dependencies

  • Requires an active connection to the Mindz API via an OAuth2 API credential.
  • The user must configure the node with valid Mindz API credentials to authenticate requests.
  • Network access to the Mindz API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Bundle ID: Ensure the Bundle ID provided exists and is correctly formatted.
    • Authentication errors: Verify that the API credentials are valid and have sufficient permissions.
    • Network or API downtime: Check connectivity and Mindz service status.
  • Error messages:

    • "Bundle not found": The specified Bundle ID does not exist; verify the ID.
    • "Unauthorized": Authentication failed; reconfigure the API credentials.
    • "Request failed": General failure; check network and API availability.

Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring stable network connections.

Links and References

  • Mindz API Documentation (example placeholder link)
  • n8n OAuth2 Credential Setup Guide
  • Mindz Support and Troubleshooting Resources

Discussion