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 "Subscription Create" operation in this node allows users to create a new subscription entity within the Mindz platform. This operation is useful for automating the setup of recurring billing or membership plans, where you define how often and for how long a customer will be billed.
Typical use cases include:
- Creating subscription plans for online courses or digital content.
- Setting up recurring billing intervals for memberships or services.
- Automating commission cycles related to subscriptions.
For example, an education platform could use this node to create monthly subscription plans for students, specifying the billing interval, frequency, and maximum number of billing cycles.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the subscription to be created (required). |
| Description | A textual description of the subscription plan. |
| Interval | Billing interval unit. Options: Days, Weeks, Months, Years. |
| Frequency | Billing frequency as a number (e.g., every 1 month, every 2 weeks). |
| Max Cycles | Maximum number of billing cycles; 0 means unlimited billing cycles. |
| Max Commission Cycles | Maximum number of commission cycles associated with the subscription. |
Output
The output JSON contains the details of the newly created subscription object as returned by the Mindz API. This typically includes fields such as subscription ID, name, description, billing interval, frequency, max cycles, and commission cycles.
If the node supports binary data output, it would represent any files or attachments related to the subscription, but based on the provided code and properties, this node primarily outputs JSON data representing the subscription entity.
Dependencies
- Requires an API key credential for authenticating with the Mindz API.
- The node depends on the Mindz platform's subscription service endpoint.
- Proper configuration of the OAuth2 or API authentication credentials in n8n is necessary.
Troubleshooting
- Missing Required Fields: If the "Name" property is not provided, the node will likely throw an error indicating a missing required parameter.
- Invalid Interval or Frequency: Providing unsupported values for interval or non-positive numbers for frequency may cause API errors.
- API Authentication Errors: Ensure that the API key or OAuth2 credentials are correctly configured and have sufficient permissions.
- Max Cycles Misconfiguration: Setting max cycles to negative numbers or invalid types might result in errors.
- Network Issues: Connectivity problems with the Mindz API endpoint can cause timeouts or failures.
To resolve these issues:
- Double-check all required input parameters.
- Validate numeric inputs for frequency and max cycles.
- Verify API credentials and permissions.
- Test network connectivity to the Mindz API.
Links and References
- Mindz API Documentation (subscription section) – [Link to official API docs]
- n8n OAuth2 Credential Setup Guide – [Link to n8n docs]
- Recurring Billing Concepts – [General resource on subscription billing]