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. This node facilitates managing mailing lists, campaigns, subscribers, templates, media, and other related resources within listmonk.
Specifically, the List - Get List operation retrieves details of a particular mailing list by its ID. This is useful when you want to fetch information about a specific list, such as its name, description, or settings, for use in workflows that manage email campaigns or subscriber segmentation.
Practical examples:
- Fetching a mailing list's details before adding or removing subscribers.
- Retrieving list metadata to display or log in an automation workflow.
- Using list information to conditionally trigger campaign sends or updates.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the mailing list object to retrieve. This is a required string input specifying which list to get. |
Output
The output of the Get List operation will be a JSON object representing the mailing list's data as returned by the listmonk API. This typically includes fields such as the list's ID, name, description, creation date, and any other metadata associated with the list.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the list, but this operation primarily returns JSON data.
Dependencies
- Requires connection to a listmonk instance via its REST API.
- Needs credentials including domain URL, username, and password for basic authentication.
- The node expects the base URL to be configured without trailing slashes; it appends
/apiautomatically. - No additional external services are required beyond the listmonk API.
Troubleshooting
- Invalid ID error: If the provided list ID does not exist or is malformed, the API will return an error. Verify the ID is correct and exists in your listmonk instance.
- Authentication errors: Ensure the API credentials (domain, username, password) are correctly set and have sufficient permissions.
- Network issues: Confirm the listmonk server is reachable from n8n and that no firewall or network restrictions block access.
- Trailing slash in domain: The node removes trailing slashes from the domain URL; if the base URL is misconfigured, requests may fail.