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 provides integration with the Mindz API, allowing users to manage various resources including emails. Specifically, for the Email resource with the Delete operation, the node deletes an email identified by its ID from a specified email list. This is useful in scenarios where you want to programmatically remove outdated or incorrect email entries from your mailing lists to maintain clean and updated contact data.
Practical examples include:
- Automatically removing unsubscribed or bounced email addresses from your marketing email lists.
- Cleaning up test or temporary emails after campaigns.
- Managing email lists dynamically based on user activity or external triggers.
Properties
| Name | Meaning |
|---|---|
| Email List ID | The unique identifier of the email list that contains the email to be deleted. |
| Email ID | The unique identifier of the email to delete from the specified email list. |
Output
The output JSON typically contains confirmation details about the deletion operation. This may include status messages or metadata confirming that the email was successfully removed from the list. The exact structure depends on the Mindz API response but generally confirms success or failure of the delete request.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API key credential.
- The node depends on proper configuration of this API authentication within n8n to authorize requests.
- Network access to the Mindz API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Email List ID or Email ID parameters will cause the operation to fail.
- Authentication errors if the API credentials are not set up correctly or have expired.
- Network connectivity problems can prevent communication with the Mindz API.
- Attempting to delete an email that does not exist in the specified list may result in an error or no-op response.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and refresh the API credentials.
- "Email not found": Verify that the Email ID and Email List ID are correct and correspond to existing records.
- "Invalid parameters": Ensure all required fields are provided and correctly formatted.
- Timeouts or network errors: Confirm network connectivity and Mindz API availability.
Links and References
- Mindz API Documentation (general reference for endpoints and operations)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)