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 integrates with the Mindz API to manage various resources, including email lists. Specifically, for the Email List - Create operation, it allows users to create a new email list within the Mindz platform. This is useful in scenarios where you want to programmatically organize contacts or subscribers into distinct groups for targeted email campaigns or communication workflows.
Practical examples include:
- Automatically creating segmented mailing lists based on user behavior or sign-up data.
- Setting up new email lists as part of onboarding processes or marketing automation.
- Managing subscriber groups dynamically from other systems integrated via n8n.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the email list to be created. This is a required string property that identifies the list. |
| Slug | An optional string used as a URL-friendly identifier or shorthand for the email list. Useful for referencing the list in URLs or APIs. |
Output
The node outputs JSON data representing the newly created email list object returned by the Mindz API. This typically includes details such as the list's unique ID, name, slug, creation timestamps, and any other metadata provided by the API.
If the node supports binary data output (not indicated here), it would represent attachments or related files, but for this operation, the output is purely JSON.
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 being accessible and the credentials having sufficient permissions to create email lists.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an empty or duplicate "Name" may result in validation errors from the API.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate misconfigured or expired API tokens; re-authenticate or update credentials.
- Validation errors about the "Name" field suggest ensuring it is non-empty and unique.
- Timeout or network errors require checking internet connectivity and Mindz API status.
Links and References
- Mindz API documentation (general reference for endpoints and data models)
- n8n OAuth2 credential setup guide
- Best practices for managing email lists and campaigns in Mindz