Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
This node integrates with a listmonk instance, a self-hosted newsletter and mailing list manager. Specifically, the "Subscriber" resource with the "Get by Email" operation allows users to search for subscribers by their email address. Since listmonk does not provide a direct API endpoint to fetch a single subscriber by email, this operation returns a list of subscribers matching the given email, typically containing one element due to the uniqueness of email addresses.
Common scenarios include:
- Retrieving subscriber details before updating or deleting them.
- Verifying if an email is already subscribed.
- Fetching subscriber information for segmentation or targeted campaigns.
Example use case: Before adding a new subscriber, you can check if the email already exists to avoid duplicates.
Properties
| Name | Meaning |
|---|---|
| Subscriber Email | The email address of the subscriber to search for. Although emails are unique in listmonk, this method returns a list of matching subscribers (usually one). |
Output
The output contains a JSON field with a list of subscriber objects that match the provided email address. Each object includes subscriber details as stored in listmonk (e.g., email, name, subscription status). Since the operation returns a list, even if only one subscriber matches, the output is always an array.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a listmonk instance via its API.
- Needs credentials including domain URL, username, and password for basic authentication.
- The node expects the listmonk API base URL to be configured correctly without trailing slashes.
Troubleshooting
- No subscribers found: If the returned list is empty, verify that the email address is correct and exists in the listmonk database.
- Authentication errors: Ensure the API credentials (domain, username, password) are valid and have sufficient permissions.
- API connectivity issues: Confirm that the listmonk instance is reachable from n8n and that the base URL is correctly set.
- Unexpected response format: If the API changes or the node version mismatches the listmonk API version, the output structure might differ.