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 perform various operations on different resources. Specifically, for the Email List resource and its List operation, the node retrieves a list of email lists from the Mindz platform. This is useful when you want to fetch multiple email lists for further processing, reporting, or integration with other systems.
Common scenarios include:
- Synchronizing email lists from Mindz into another marketing or CRM system.
- Displaying available email lists for selection in workflows.
- Automating campaigns by dynamically retrieving lists based on criteria.
Example: You might use this node to get the first 50 email lists sorted by creation date ascending, optionally filtering by a search term, then iterate over them to send targeted emails.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return (minimum 1). |
| Offset | Number of results to skip before starting to collect the output. |
| Sort By | Field to sort results by. Options: Created At, ID, Name, Updated At. |
| Sort Direction | Direction to sort results by. Options: Ascending, Descending. |
| Search | Search term to filter results by matching text. |
Output
The node outputs JSON data containing the list of email lists retrieved from the Mindz API. Each item in the output array represents an email list object with its properties as returned by the API.
If the API supports binary data related to email lists (e.g., attachments or exports), it would be included in the binary output field, but this is not indicated in the provided code or properties.
Dependencies
- Requires an active connection to the Mindz API using OAuth2 authentication (an API key credential).
- The node depends on the Mindz API being accessible and properly configured.
- No additional external services are required beyond the Mindz API.
Troubleshooting
Common issues:
- Authentication failures due to invalid or expired API tokens.
- Network connectivity problems preventing access to the Mindz API.
- Invalid parameter values such as negative limits or offsets.
- Empty results if the search term filters out all email lists.
Error messages:
- Authentication errors typically indicate the need to refresh or reconfigure credentials.
- Validation errors may occur if "Limit" is set below 1.
- API errors might indicate rate limiting or server-side issues; retry after some time.
Links and References
- Mindz API documentation (general reference for endpoints and parameters) — [URL not provided in source]
- n8n OAuth2 credential setup guide — https://docs.n8n.io/credentials/oauth2/
- n8n node development documentation — https://docs.n8n.io/integrations/creating-nodes/