Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Subscriber → Modify a Subscriber
AI-generatedOverview
The node integrates with a Listmonk instance, focusing here on the "Modify a Subscriber" operation within the Subscriber resource. It allows users to update existing subscriber details such as their name, email, status, list memberships, and custom attributes. This is useful in scenarios where subscriber information needs to be kept current, for example, updating contact details, changing subscription preferences, or managing subscriber statuses (enabled, disabled, blocklisted).
Practical examples include:
- Correcting a subscriber's email address.
- Changing a subscriber's status to blocklisted after unsubscribing.
- Adding or removing subscribers from specific mailing lists.
- Updating custom attributes like user preferences or demographic data.
Properties
| Name | Meaning |
|---|---|
| Name | The subscriber's full name. Required for modifying subscriber details. |
| Subscriber ID | The unique numeric identifier of the subscriber to modify. |
| The subscriber's email address. Must be a valid email format. | |
| Status | The subscriber's status. Options: Enabled, Disabled, Blocklisted. |
| Lists | JSON array specifying the mailing lists to which the subscriber should be added. |
| Attributes | JSON object containing custom subscriber attributes (key-value pairs). |
| Preconfirm Subscriptions | Boolean flag indicating if subscriptions are preconfirmed (true means no double opt-in emails sent). |
Output
The node outputs JSON data representing the result of the modification operation. Typically, this includes confirmation of the updated subscriber details or an acknowledgment of success. If the operation fails, error information will be included in the output.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Listmonk API instance.
- Needs credentials including domain URL, username, and password for basic authentication.
- The node expects the Listmonk API to be accessible and properly configured to allow subscriber modifications.
Troubleshooting
- Invalid Subscriber ID: If the provided subscriber ID does not exist, the API will return an error. Verify the subscriber ID before attempting modification.
- Invalid Email Format: The node validates email format; entering an invalid email will cause validation errors. Ensure emails conform to standard formats.
- Authentication Errors: Incorrect API credentials or domain URL will prevent successful API calls. Double-check credential configuration.
- JSON Parsing Issues: The Lists and Attributes fields expect valid JSON input. Malformed JSON will cause errors. Use proper JSON syntax.
- Status Value Errors: Only the specified status options are accepted. Using unsupported values will cause failures.