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
This node interacts with the Mindz API to manage and retrieve data related to email campaign excluded lists. Specifically, the Email Campaign Excluded List - List operation fetches a paginated list of contacts or entries that have been excluded from a particular email campaign. This is useful for marketers or administrators who want to review or audit which recipients are excluded from receiving certain email campaigns, ensuring compliance with preferences or regulations.
Practical examples:
- Retrieve all users who opted out or were excluded from an email campaign before sending follow-up messages.
- Audit exclusion lists to verify that unsubscribed users are properly excluded.
- Integrate with other systems to synchronize exclusion data for reporting or CRM updates.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign whose excluded list you want to retrieve. |
| Limit | Maximum number of results to return in one request (minimum 1). Defaults to 50. |
| Offset | Number of results to skip before starting to collect the output (for pagination). Defaults to 0. |
Output
The node outputs JSON data representing the list of excluded entries for the specified email campaign. The structure typically includes details about each excluded contact or entry, such as identifiers, exclusion reasons, timestamps, or related metadata depending on the Mindz API response schema.
If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but based on the provided code and context, the output is purely JSON.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential configured in n8n.
- The node depends on the Mindz API endpoints for email campaign excluded lists.
- Proper permissions and valid credentials are necessary to access email campaign data.
Troubleshooting
Common issues:
- Invalid or missing Email Campaign ID will cause the API call to fail.
- Pagination parameters (
limitandoffset) set incorrectly may result in empty or incomplete data. - Authentication errors if the OAuth2 token is expired or misconfigured.
- Network or API downtime can cause request failures.
Error messages and resolutions:
- "Unauthorized" or "Invalid credentials": Check and refresh the API authentication token.
- "Resource not found": Verify the Email Campaign ID is correct and exists.
- "Limit must be at least 1": Ensure the limit parameter is set to 1 or higher.
- Timeouts or network errors: Confirm network connectivity and Mindz API status.
Links and References
- Mindz API Documentation (hypothetical link, replace with actual if available)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- General n8n Node Development: https://docs.n8n.io/integrations/creating-nodes/