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, specifically allowing operations on various resources including emails. For the Email - Get operation, it retrieves detailed information about a specific email within a given email list. This is useful when you need to fetch and use email data stored in Mindz, such as for reporting, further processing, or integration with other systems.
Practical examples:
- Fetching an email's details by its ID to display or analyze its content.
- Retrieving email metadata before performing updates or deletions.
- Integrating email data into automated workflows for marketing or communication purposes.
Properties
| Name | Meaning |
|---|---|
| Email List ID | The unique identifier of the email list that contains the target email. |
| Email ID | The unique identifier of the email to retrieve from the specified email list. |
Output
The output will contain a JSON object representing the retrieved email's data. This typically includes all relevant fields of the email such as subject, body, sender, recipients, status, timestamps, and any other metadata provided by the Mindz API for an email entity.
If the node supports binary data (not indicated here), it would represent attachments or email content in binary form, but this is not explicitly shown in the provided code or properties.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based credential.
- The node depends on the Mindz API being accessible and the credentials having sufficient permissions to read email data.
- No additional environment variables or external services are explicitly required beyond the configured Mindz API authentication.
Troubleshooting
Common issues:
- Invalid or missing Email List ID or Email ID parameters will cause the operation to fail.
- Authentication errors if the OAuth2 token is expired or invalid.
- Network connectivity problems preventing access to the Mindz API.
- Permissions issues if the authenticated user does not have rights to access the specified email or list.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Refresh or reconfigure the API credentials.
- "Email not found": Verify that the Email List ID and Email ID are correct and exist in Mindz.
- "Network error": Check internet connection and API endpoint availability.
- "Missing required parameter": Ensure both Email List ID and Email ID are provided and non-empty.
Links and References
- Mindz API Documentation (general reference for endpoints and data structures)
- OAuth2 Authentication Guide (for setting up API credentials)
- n8n Documentation on creating custom nodes and using credentials