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 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 subscription plans are excluded from an ongoing or planned email campaign.
- Automating reports on email campaign targeting exclusions.
- Integrating with other systems to synchronize exclusion lists for campaigns.
Practical example:
You have an email campaign promoting a new feature but want to exclude users on certain subscription plans from receiving it. Using this node's List operation, you can fetch all excluded plans for that campaign and verify or audit the exclusions programmatically.
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 one response (minimum 1, default 50). |
| Offset | Number of excluded plans to skip before starting to collect the result set (default 0). |
Output
The output contains a JSON array of objects representing the excluded plans for the specified email campaign. Each object typically includes details such as plan identifiers and possibly metadata about the exclusion.
If the node supports pagination via limit and offset, the output will reflect the subset of excluded plans accordingly.
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.
- The node depends on proper configuration of this API authentication within n8n.
- No additional external services are required beyond the Mindz API.
Troubleshooting
Common issues:
- Invalid or missing Email Campaign ID: The API will not return results if the campaign ID is incorrect or not provided.
- Authentication errors: Ensure the OAuth2 API credentials are valid and have sufficient permissions.
- Pagination parameters (
limitandoffset) out of range or invalid may cause errors or empty responses.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and token validity.
- "Resource not found": Verify the Email Campaign ID exists in the Mindz system.
- "Invalid parameter" related to limit/offset: Adjust these values to be within allowed ranges.
Links and References
- Mindz API Documentation (hypothetical link)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- Pagination best practices: https://restfulapi.net/pagination/
This summary is based solely on static analysis of the provided source code and property definitions.