Actions8
Update Subscriber
AI-generatedOverview
The "Update Subscriber" operation in this node allows you to modify the details of an existing subscriber in your Listmonk email marketing system. This includes updating their email address, name, subscription status, the lists they belong to, and any custom attributes associated with them.
This operation is useful when you need to keep your subscriber data current, such as correcting an email address, changing a subscriber's status (e.g., enabling or disabling), or updating their preferences and attributes without creating a new subscriber record.
Practical example:
If a subscriber changes their email or wants to be removed from certain mailing lists, you can use this operation to update their information accordingly, ensuring your campaigns target the right audience.
Properties
| Name | Meaning |
|---|---|
| Subscriber ID | The unique numeric identifier of the subscriber to update. |
| Subscriber Email | The subscriber's email address. Must be a valid email format. |
| Subscriber Name | The full name of the subscriber. Optional field. |
| Subscriber Status | The current status of the subscriber. Options: Enabled, Disabled, Blocklisted. |
| Subscriber Lists (JSON) | A JSON array of list IDs that the subscriber should be subscribed to (e.g., [1, 2, 3]). |
| Subscriber Attributes (JSON) | A JSON object containing custom key-value pairs for additional subscriber attributes. |
Output
The node outputs the response from the Listmonk API after attempting to update the subscriber. The output is a JSON object representing the updated subscriber data, including fields like email, name, status, lists, and attributes as stored in Listmonk.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to a Listmonk instance via its API.
- Needs credentials including domain URL, username, and password for authentication.
- The node expects the Listmonk API to be accessible and properly configured.
Troubleshooting
- Invalid Subscriber ID: If the subscriber ID does not exist, the API will likely return an error indicating the subscriber was not found. Verify the ID before updating.
- Invalid Email Format: The subscriber email must match a valid email regex pattern; otherwise, the node will reject the input.
- Authentication Errors: Ensure the API credentials are correct and have sufficient permissions to update subscribers.
- Malformed JSON: The
subscriberListsandsubscriberAttributesfields must be valid JSON. Invalid JSON will cause request failures. - Network Issues: Connectivity problems with the Listmonk server will prevent updates; check network and server status.
Links and References
- Listmonk Official Documentation – For detailed API usage and subscriber management.
- Listmonk API Reference – Specific endpoints and payload formats for subscriber updates.