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 email campaign plans. Specifically, the Create operation under the Email Campaign Plan resource allows users to add a new plan to an existing email campaign. This is useful for marketing automation scenarios where you want to dynamically associate different plans or offers with your email campaigns.
For example, if you have an email campaign targeting a specific audience and want to include a new subscription plan or promotional offer as part of that campaign, this node operation lets you programmatically link that plan to the campaign.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign to which the plan will be added. |
| Plan ID | The unique identifier of the plan that you want to add to the specified email campaign. |
Output
The output JSON contains the response from the Mindz API after attempting to create the association between the email campaign and the plan. Typically, this includes confirmation details such as IDs, status, timestamps, or any metadata related to the newly created email campaign plan entry.
If the node supports binary data output (not indicated here), it would represent any file or media content returned by the API, but in this case, the output is purely JSON-based.
Dependencies
- Requires an active connection to the Mindz API.
- Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests.
- The node depends on the Mindz API endpoints related to email campaign plans.
Troubleshooting
- Invalid Email Campaign ID or Plan ID: If either ID is incorrect or does not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Ensure the API credentials are valid and have sufficient permissions to modify email campaigns.
- Network Issues: Connectivity problems can cause timeouts or failed requests; check network access to the Mindz API.
- API Rate Limits: Excessive requests may trigger rate limiting; consider adding delays or retries.
Links and References
- Mindz API Documentation (general reference for email campaign management)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)