Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
The node "Listmonk" allows interaction with a listmonk instance, which is an open-source self-hosted newsletter and mailing list manager. Specifically, the "Update List" operation updates an existing mailing list on the listmonk server by sending a JSON body containing the updated data for that list.
This node is beneficial in scenarios where you want to programmatically manage your mailing lists, such as updating list details or settings without manually accessing the listmonk UI. For example, you could automate updating list metadata or configuration based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the list to update. This is required to specify which list to modify. |
| Json Body | The JSON object containing the fields and values to update on the list. This can include any valid list properties supported by listmonk. |
Output
The node outputs JSON data representing the response from the listmonk API after attempting to update the list. This typically includes the updated list object or status information confirming the update.
No binary data output is indicated for this operation.
Dependencies
- Requires access to a running listmonk instance.
- Requires credentials for authentication: a domain URL, username, and password.
- The node uses HTTP Basic Authentication to communicate with the listmonk API.
- The base URL for API requests is constructed from the provided domain credential.
Troubleshooting
- Invalid ID: If the provided list ID does not exist, the API will likely return an error indicating the resource was not found. Verify the ID is correct.
- Authentication errors: Incorrect username or password will cause authentication failures. Ensure credentials are accurate.
- Malformed JSON Body: Sending invalid JSON or unsupported fields may result in API errors. Validate the JSON structure before sending.
- Network issues: Connectivity problems to the listmonk server will cause request failures. Check network and server availability.
Links and References
- listmonk Official Documentation
- listmonk API Reference (for details on list update payloads)