Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Subscriber → Get by Email
AI-generatedOverview
The node integrates with a listmonk instance, an email marketing and newsletter management platform. 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 in listmonk.
This node is beneficial when you want to verify if a subscriber exists, retrieve subscriber details for further processing, or synchronize subscriber data from other systems based on email addresses.
Practical example:
You have a signup form on your website and want to check if the user’s email already exists in your mailing list before adding them. Using this node, you can query the subscriber by email and decide whether to update existing data or create a new subscriber.
Properties
| Name | Meaning |
|---|---|
| Subscriber Email | The email address of the subscriber to search for. Must be a valid email format. Returns a list of subscribers matching this email (usually one). |
Output
The output contains a JSON field with a list of subscriber objects that match the provided email address. Each subscriber object includes details such as subscriber ID, email, name, subscription status, and any other metadata stored in listmonk.
Since the operation returns a list, even though it usually contains only one subscriber due to email uniqueness, users should handle the response accordingly.
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 authentication.
- The node expects the listmonk API to be accessible and properly configured to allow subscriber queries.
Troubleshooting
- No subscribers found: If the returned list is empty, the email does not exist in the listmonk database. Verify the email input is correct and properly formatted.
- Invalid email format error: The node validates the email format using regex. Ensure the email matches standard email patterns.
- Authentication errors: Check that the API credentials (domain, username, password) are correctly set and have sufficient permissions.
- Network or API errors: Confirm the listmonk instance is reachable and the API endpoint is correct.
Links and References
- listmonk Official Documentation – For detailed API and platform information.
- Email Validation Regex Reference – Explanation of the email validation pattern used.