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 interacts with the Mindz API to manage subscriptions among other resources. Specifically, for the Subscription - Get operation, it retrieves detailed information about a specific subscription plan by its ID. This is useful in scenarios where you need to fetch subscription details such as plan features, status, or metadata for reporting, validation, or further processing within an automation workflow.
Practical examples include:
- Fetching subscription details before updating user access.
- Validating subscription status before granting course enrollment.
- Retrieving subscription info to synchronize with external billing systems.
Properties
| Name | Meaning |
|---|---|
| Subscription Plan ID | The unique identifier of the subscription plan to retrieve. This is a required string. |
Output
The output will be a JSON object containing the details of the requested subscription plan. This typically includes fields such as subscription ID, name, status, pricing, features, and any other metadata provided by the Mindz API for that subscription.
If the node supports binary data output (not indicated here), it would represent associated files or documents related to the subscription, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential configured in n8n.
- The node depends on the Mindz API being accessible and the credentials having sufficient permissions to read subscription data.
Troubleshooting
Common issues:
- Invalid or missing Subscription Plan ID will cause the API call to fail.
- Expired or invalid API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API communication.
Error messages and resolutions:
- "Subscription not found": Verify the Subscription Plan ID is correct and exists.
- "Authentication failed": Check that the API key credential is valid and has not expired.
- "Network error" or timeout: Ensure your network allows outbound requests to the Mindz API endpoint.
Links and References
- Mindz API Documentation (for subscription endpoints) — [Insert actual URL if available]
- n8n OAuth2 Credential Setup Guide — https://docs.n8n.io/credentials/oauth2/