Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
List → Update List
AI-generatedOverview
The node integrates with a listmonk instance, a self-hosted newsletter and email marketing platform. It allows users to manage mailing lists, subscribers, campaigns, media, and templates programmatically within n8n workflows.
Specifically, the Update List operation updates an existing mailing list in listmonk by sending a JSON body with the desired changes to the API endpoint corresponding to that list's ID.
Common scenarios include:
- Modifying list details such as name, description, or settings.
- Automating updates to mailing lists based on external data or triggers.
- Integrating list management into broader marketing automation workflows.
Example: Automatically update a mailing list’s attributes when a related CRM record changes.
Properties
| Name | Meaning |
|---|---|
| Json Body | The JSON object containing the fields and values to update for the list. |
| ID | The unique numeric identifier of the list to update. Must be a valid number and required. |
Output
The node outputs JSON data representing the updated list object as returned by the listmonk API after the update operation. This typically includes the list's current properties reflecting the applied changes.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a listmonk instance via its REST API.
- Needs credentials including domain URL, username, and password for basic authentication.
- The base URL is constructed from the provided domain credential, ensuring no trailing slash.
- The node sends requests with
AcceptandContent-Typeheaders set toapplication/json.
Troubleshooting
- Invalid ID error: Ensure the ID property is a valid number corresponding to an existing list in listmonk.
- Authentication failures: Verify that the API credentials (domain, username, password) are correct and have sufficient permissions.
- Malformed JSON Body: The JSON body must be well-formed and contain valid fields accepted by the listmonk API; otherwise, the API may reject the request.
- Network issues: Confirm that the listmonk instance is reachable from the n8n environment.
- API errors: Check the response message for specific API error details and adjust the input accordingly.