Actions30
- Campaign Actions
- List Actions
- Template Actions
- Subscriber Actions
- List Segment Actions
- Transactional Email Actions
Subscriber → Update by Email
AI-generatedOverview
This node operation updates a subscriber in a MailWizz mailing list identified by their email address. It allows changing the subscriber's email, status (e.g., confirmed, unconfirmed, unsubscribed, blacklisted), and additional custom fields. This operation is useful for managing subscriber information dynamically, such as correcting email addresses, updating subscription status, or adding custom data fields for targeted marketing campaigns.
Use Case Examples
- Updating a subscriber's email address and status in a specific mailing list.
- Adding or modifying custom subscriber fields like first name or preferences.
- Changing a subscriber's status to unsubscribed based on user request.
Properties
| Name | Meaning |
|---|---|
| List ID | Identifier of the mailing list containing the subscriber to update. |
| Subscriber Email | Current email address of the subscriber to identify them in the list. |
| Subscriber Status | Desired subscription status to set for the subscriber (confirmed, unconfirmed, unsubscribed, blacklisted). |
| New Subscriber Email | Optional new email address to update the subscriber's email. |
| Subscriber Fields | Additional custom field tag/value pairs to include in the subscriber's data. |
| Subscriber Data (JSON) | Advanced JSON object containing MailWizz field tags as keys, merged with other subscriber fields for detailed subscriber data. |
Output
JSON
json- Response object from MailWizz API containing the updated subscriber details or operation result.
Dependencies
- MailWizz API with appropriate API key credentials for authentication.
Troubleshooting
- Ensure the List ID and Subscriber Email are correctly provided; missing or incorrect values will cause errors.
- Subscriber must exist in the specified list; otherwise, the node will throw a 'subscriber not found' error.
- JSON fields must be valid JSON; invalid JSON in 'Subscriber Data (JSON)' will cause parsing errors.
- If updating the email, ensure the new email is valid and not already in use to avoid conflicts.
- API rate limits or connectivity issues with MailWizz can cause request failures; check network and API status.
Links
- MailWizz API Subscriber Documentation - Official MailWizz API documentation for managing subscribers, including update operations.