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 resources such as enrollments, users, teams, courses, and more. Specifically, for the Enroll resource with the Delete operation, this node enables the deletion of an enrollment record by its unique identifier. This is useful in scenarios where you need to programmatically remove a user's enrollment from a course or program within the Mindz platform.
Practical examples include:
- Automatically unenrolling users who have canceled their subscription.
- Cleaning up test or expired enrollments in bulk.
- Integrating with external systems to synchronize enrollment status by deleting outdated records.
Properties
| Name | Meaning |
|---|---|
| Enroll ID | The unique identifier of the enrollment to delete. This is a required string input. |
Output
The output of the node after executing the Delete operation on an enrollment typically contains JSON data reflecting the result of the deletion request. This may include confirmation of successful deletion or details about the deleted enrollment. The exact structure depends on the Mindz API response but generally confirms that the specified enrollment has been removed.
If the node supports binary data output (not indicated here), it would represent any files or attachments related to the enrollment, but this is unlikely for a delete 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 properly authenticated.
- No additional external services are required beyond the Mindz API.
Troubleshooting
Common issues:
- Invalid or missing Enroll ID: Ensure the Enroll ID provided is correct and exists in the Mindz system.
- Authentication errors: Verify that the API credentials are valid and have sufficient permissions to delete enrollments.
- Network or API downtime: Check connectivity and Mindz API status.
Common error messages:
- "Enrollment not found": The provided Enroll ID does not exist; verify the ID.
- "Unauthorized" or "Authentication failed": The API key or token is invalid or expired; reauthenticate.
- "Permission denied": The API user lacks rights to delete enrollments; check user roles and permissions.
- "API rate limit exceeded": Too many requests sent in a short time; implement retry logic or reduce request frequency.
Resolving these usually involves verifying inputs, refreshing credentials, and ensuring proper API access rights.
Links and References
- Mindz API Documentation (replace with actual URL if available)
- n8n OAuth2 Credential Setup Guide
- General REST API best practices for error handling and authentication