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-related data within the Mindz platform. Specifically, for the Email resource and the Get operation, it retrieves detailed information about a specific email identified by its Email ID within a given Email List.
This node is beneficial in scenarios where you need to programmatically access email details from your Mindz account, such as fetching email content, status, or metadata for automation workflows, reporting, or integration with other systems.
Practical example:
You have an automated workflow that triggers when a new email is sent in a campaign. Using this node, you can fetch the full details of that email by specifying the Email List ID and Email ID, then use the retrieved data to update a CRM system or send notifications.
Properties
| Name | Meaning |
|---|---|
| Email List ID | The unique identifier of the email list to which the email belongs. |
| Email ID | The unique identifier of the specific email to retrieve within the specified email list. |
Output
The node outputs JSON data representing the detailed information of the requested email. This typically includes fields such as the email's subject, body content, sender information, status, timestamps, and any other metadata provided by the Mindz API for that email.
If the node supports binary data output (not indicated explicitly here), it would represent attachments or email content in binary form; however, based on the provided code and properties, the primary output is structured JSON data about the email.
Dependencies
- Requires an active connection to the Mindz API using an OAuth2-based API key credential.
- The node depends on proper configuration of the Mindz OAuth2 credentials within n8n.
- Network connectivity to the Mindz API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Email List ID or Email ID parameters will cause the node to fail retrieving the email.
- Authentication errors if the OAuth2 credentials are expired or misconfigured.
- Network or API downtime may result in request failures.
Error messages and resolutions:
- "Authentication failed" — Verify that the OAuth2 credentials are correctly set up and have not expired.
- "Email not found" — Check that the Email List ID and Email ID are correct and exist in your Mindz account.
- "Network error" — Ensure stable internet connection and that the Mindz API service is operational.
Links and References
- Mindz API Documentation (hypothetical link, replace with actual if available)
- n8n OAuth2 Credential Setup Guide
- n8n Community Forum for troubleshooting and examples