Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Subscriber → Get Subscriber by ID
AI-generatedOverview
This node integrates with a listmonk instance, an email marketing and newsletter management platform. Specifically, the "Get Subscriber by ID" operation retrieves detailed information about a single subscriber using their unique numeric ID. This is useful for scenarios where you need to fetch subscriber details for verification, reporting, or further processing within an automation workflow.
Practical examples include:
- Fetching subscriber data before updating their subscription preferences.
- Retrieving subscriber info to personalize email campaigns.
- Validating subscriber existence before performing deletion or other operations.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the subscriber to retrieve. Must be a valid number. |
Output
The output contains a JSON object representing the subscriber's data as returned by the listmonk API. This typically includes fields such as subscriber ID, email address, subscription status, and any custom attributes associated with the subscriber.
No binary data output is expected from 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 node expects the API endpoint base URL to be configured correctly in the credentials.
Troubleshooting
- Invalid ID error: If the provided ID is not a valid number or does not exist, the API will likely return an error. Ensure the ID is correct and corresponds to an existing subscriber.
- Authentication errors: Incorrect or missing credentials will cause authentication failures. Verify that the API credentials are set properly.
- Network issues: Connectivity problems to the listmonk server will prevent data retrieval. Check network access and the correctness of the domain URL.
- API changes: If the listmonk API version changes, some fields or endpoints might differ, causing unexpected errors.