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 "Email - Update" operation in this node allows users to modify details of an existing email contact within a specified email list. This is useful for keeping contact information current, managing subscription status, or correcting errors in stored email data.
Common scenarios include:
- Updating a subscriber's email address or name after they notify you of changes.
- Changing the subscription status (subscribed/unsubscribed) of a contact based on their preferences.
- Maintaining accurate and up-to-date contact lists for targeted email campaigns.
For example, if a user wants to update the first and last name of a contact in a mailing list or mark them as unsubscribed, this operation facilitates those changes programmatically.
Properties
| Name | Meaning |
|---|---|
| Email List ID | The unique identifier of the email list that contains the email contact to be updated. |
| Email ID | The unique identifier of the specific email contact to update within the email list. |
| Email Address | The new or updated email address of the contact. |
| First Name | The updated first name of the contact. |
| Last Name | The updated last name of the contact. |
| Is Subscribed | Boolean flag indicating whether the contact is subscribed (true) or unsubscribed (false) to the email list. |
Output
The node outputs JSON data representing the updated email contact record. This typically includes fields such as the email ID, email address, first and last names, subscription status, and possibly metadata about the update operation.
If the node supports binary data output (not indicated here), it would represent attachments or related files, but for this operation, the focus is on JSON data reflecting the updated contact information.
Dependencies
- Requires an API authentication token or OAuth2 credential configured in n8n to connect securely with the Mindz API.
- Depends on the Mindz platform's email list management API endpoints to perform update operations.
- Proper permissions on the API key or OAuth2 token are necessary to modify email contacts.
Troubleshooting
- Invalid Email List ID or Email ID: If these identifiers are incorrect or do not exist, the API will likely return an error indicating the resource was not found. Verify IDs before running the node.
- Permission Denied: Insufficient API credentials or scopes can cause authorization errors. Ensure the connected credential has rights to update email contacts.
- Invalid Email Format: Providing an improperly formatted email address may result in validation errors. Use valid email formats.
- Missing Required Fields: The operation requires both Email List ID and Email ID; omitting these will cause failures.
- API Rate Limits: Frequent updates might hit rate limits imposed by the Mindz API. Implement retry logic or reduce request frequency if needed.
Links and References
- Mindz API Documentation (general reference for email list and contact management)
- n8n OAuth2 Credential Setup Guide
- Best Practices for Managing Email Lists and Contacts