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 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.
- Integrating with other systems to sync contact groups dynamically.
- Setting up new marketing or notification lists as part of an automated onboarding process.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the email list to be created. This is a required string that identifies the list. |
| Slug | An optional string used as a URL-friendly identifier or shorthand for the email list. |
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 possibly metadata related to the list.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential.
- The node depends on the Mindz API being accessible and properly authenticated.
- No additional external services are explicitly required beyond the Mindz API.
Troubleshooting
- Authentication errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and has sufficient permissions.
- Validation errors: Missing the required "Name" property will cause the API to reject the request. Ensure all mandatory fields are provided.
- API connectivity: Network issues or API downtime can cause failures; check network access and Mindz service status.
- Slug conflicts: If the slug is not unique or invalid, the API might return an error. Use unique and URL-safe slugs.
Links and References
- Mindz API documentation (general reference for endpoints and data models)
- n8n OAuth2 credential setup guide (for configuring API authentication)
Note: Specific URLs are not included as they depend on the Mindz platform documentation location.