Actions9
- List Actions
- Subscriber Actions
- Transactional Message Actions
Overview
The node interacts with the Listmonk service to retrieve subscriber information. Specifically, the "Subscriber Get" operation allows users to fetch details about a subscriber by either their unique subscriber ID or their email address. This is useful in scenarios where you want to look up subscriber data for marketing campaigns, user management, or analytics within Listmonk.
Practical examples include:
- Retrieving subscriber details before sending a targeted email campaign.
- Verifying if a subscriber exists based on their email.
- Fetching subscriber metadata for integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Subscriber Identifier | Choose how to identify the subscriber: either by "Subscriber ID" or "Subscriber Email". |
| Subscriber ID | The numeric ID of the subscriber (used only if "Subscriber ID" is selected). |
| Subscriber Email | The email address of the subscriber (used only if "Subscriber Email" is selected). |
Output
The node outputs JSON data representing the subscriber's details as returned by the Listmonk API. This typically includes fields such as subscriber ID, email, name, subscription status, and any custom attributes associated with the subscriber.
If the subscriber is found, the output JSON will contain the subscriber object; if not found, it may return an error or empty result depending on the API response.
The node does not output binary data.
Dependencies
- Requires connection to a Listmonk service instance.
- Needs an API key credential configured in n8n to authenticate requests to the Listmonk API.
- The base URL for the API is derived from the host provided in the credentials.
Troubleshooting
Common issues:
- Incorrect subscriber identifier type selected (e.g., choosing Subscriber ID but providing an email).
- Invalid or missing API credentials leading to authentication errors.
- Subscriber not found if the provided ID or email does not exist in Listmonk.
Error messages:
- Authentication failures usually indicate invalid or missing API keys.
- Not found errors mean the subscriber does not exist with the given identifier.
- Validation errors occur if required properties are missing or incorrectly formatted.
To resolve these:
- Verify that the correct subscriber identifier option is selected and the corresponding value is provided.
- Ensure API credentials are correctly set up and have necessary permissions.
- Double-check subscriber identifiers for typos or incorrect values.