Actions116
- 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
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- Enroll 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 current subscription details for reporting, validation, or further processing within an automation workflow.
Practical examples include:
- Fetching subscription details to verify user access rights.
- Retrieving subscription metadata before updating or canceling a subscription.
- Integrating subscription data into CRM or billing systems.
Properties
| Name | Meaning |
|---|---|
| Subscription Plan ID | The unique identifier of the subscription plan to retrieve. This is a required string. |
Output
The node outputs JSON data representing the subscription plan details fetched from the Mindz API. The structure typically includes fields such as subscription ID, name, status, pricing, duration, and any other metadata associated with the subscription plan.
If the node supports binary data output (not indicated here), it would represent related files or attachments linked 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 that the Subscription Plan ID is correct and exists in the Mindz system.
- "Authentication failed": Check that the API key credential is valid and has not expired.
- 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 subscription endpoints)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)