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 lists. Specifically, the Email Campaign List - List operation retrieves a paginated list of email campaign lists associated with a specified email campaign ID. This is useful for scenarios where you want to fetch and process multiple email campaign lists programmatically, such as syncing them with another system, analyzing campaign reach, or automating follow-up actions based on the lists.
Practical examples:
- Fetching all subscriber lists linked to a particular email campaign to export or analyze subscriber engagement.
- Automating reporting workflows that require up-to-date information about email campaign lists.
- Integrating Mindz email campaign data into CRM or marketing automation platforms.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign whose lists you want to retrieve. |
| Limit | Maximum number of results to return in one request (minimum 1, default 50). |
| Offset | Number of results to skip before starting to collect the output (minimum 0, default 0). |
Output
The node outputs JSON data representing the retrieved email campaign lists. Each item in the output corresponds to an individual email campaign list associated with the specified email campaign ID. The exact structure depends on the Mindz API response but typically includes identifiers, names, and metadata related to each email campaign list.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the email campaign lists, but this operation primarily deals with JSON data.
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 being accessible and the provided email campaign ID being valid.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing Email Campaign ID: The API will likely return an error if the ID is incorrect or not provided.
- API authentication errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions.
- Pagination misconfiguration: Setting
limittoo high oroffsetincorrectly may result in empty or partial data sets.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and refresh the API credentials.
- "Resource not found" or "Invalid Email Campaign ID": Verify the campaign ID exists in your Mindz account.
- "Rate limit exceeded": Reduce request frequency or implement retry logic with delays.
Links and References
- Mindz API Documentation (hypothetical link as actual URL is not provided)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- Pagination best practices in APIs: https://www.baeldung.com/rest-api-pagination-in-spring