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 MindzPay Subscription "Get" operation node retrieves detailed information about a specific subscription within a MindzPay account. This node is useful when you need to fetch the current status, details, or metadata of a particular subscription by providing its unique identifier along with the associated account ID.
Common scenarios:
- Checking the status or details of a user's subscription for billing or support purposes.
- Integrating subscription data into dashboards or reports.
- Validating subscription existence before performing further actions like cancellation or suspension.
Example use case:
You have a system that manages user subscriptions and want to display subscription details in your CRM whenever a customer requests support. Using this node, you can fetch the subscription info by passing the account and subscription IDs.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the MindzPay account under which the subscription exists. |
| Subscription ID | The unique identifier of the subscription you want to retrieve details for. |
Output
The node outputs JSON data representing the subscription details retrieved from the MindzPay API. This typically includes fields such as subscription status, start and end dates, plan details, payment information, and any other metadata related to the subscription.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the subscription, but this is not applicable for the "Get" operation.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential configured in n8n.
- The node depends on the MindzPay API being accessible and the provided account and subscription IDs being valid.
- No additional external dependencies are required beyond the Mindz API credentials.
Troubleshooting
- Invalid Account or Subscription ID: If either ID is incorrect or does not exist, the node will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Ensure the OAuth2 API credential is correctly set up and has sufficient permissions to access subscription data.
- API Rate Limits: Frequent calls may hit API rate limits; consider adding delays or handling retries.
- Network Issues: Connectivity problems with the Mindz API endpoint will cause failures; check network settings and API availability.
Links and References
- Mindz API Documentation (hypothetical link as no real URL provided)
- OAuth2 Authentication setup in n8n: https://docs.n8n.io/credentials/oauth2/
- n8n Node Development Guide: https://docs.n8n.io/integrations/creating-nodes/