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 "Email Campaign Excluded Plan" resources, specifically supporting the List operation. This operation retrieves a list of plans that are excluded from a specified email campaign. It is useful when you want to see which subscription plans have been explicitly excluded from receiving a particular email campaign.
Common scenarios:
- Marketing teams reviewing which customer subscription plans are excluded from an ongoing or planned email campaign.
- Automating reports or dashboards that track exclusions in email marketing strategies.
- Integrating with other systems to synchronize exclusion lists for campaigns.
Practical example:
You have an email campaign targeting users but want to exclude certain subscription plans (e.g., free trial plans). Using this node's List operation, you can fetch all excluded plans for that campaign and use the data to adjust your targeting or analyze campaign reach.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign for which to list excluded plans. |
| Limit | Maximum number of excluded plans to return in the response. |
| Offset | Number of excluded plans to skip before starting to collect the result set (pagination). |
Output
The node outputs JSON data containing the list of excluded plans for the specified email campaign. Each item in the output typically represents one excluded plan with its associated details as returned by the Mindz API.
If the API supports pagination, the output respects the limit and offset parameters to control the size and position of the returned list.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Mindz API using an OAuth2-based API key credential configured in n8n.
- The node depends on the Mindz API endpoint that manages email campaign exclusions.
- Proper permissions and valid credentials are necessary to access email campaign exclusion data.
Troubleshooting
- Invalid or missing Email Campaign ID: The node requires a valid campaign ID; ensure it is correctly provided and exists in the Mindz system.
- API authentication errors: Verify that the OAuth2 API credentials are correctly set up and have not expired.
- Pagination issues: If the limit or offset values are out of range, the API might return empty results or errors. Adjust these values accordingly.
- Network or connectivity problems: Ensure that n8n can reach the Mindz API endpoints without firewall or proxy restrictions.
Links and References
- Mindz API Documentation (replace with actual URL if available)
- n8n OAuth2 Credential Setup Guide
- General n8n Node Development Documentation