Actions12
Subscriber → Get By ID
AI-generatedOverview
This node operation retrieves a subscriber's details from the Listmonk service by either their subscriber ID or subscriber email. It is useful for scenarios where you need to fetch specific subscriber information for further processing, such as updating subscriber data, sending targeted communications, or analyzing subscriber behavior.
Use Case Examples
- Fetch subscriber details by subscriber ID to update their profile.
- Retrieve subscriber information by email to verify subscription status.
Properties
| Name | Meaning |
|---|---|
| Subscriber Identifier | Choose how to identify the subscriber, either by Subscriber ID or Subscriber Email. |
| Subscriber ID | The unique ID of the subscriber to retrieve. Required if Subscriber Identifier is set to Subscriber ID. |
| Subscriber Email | The email address of the subscriber to retrieve. Required if Subscriber Identifier is set to Subscriber Email. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
subscriberid- The unique identifier of the subscriber.email- The email address of the subscriber.name- The name of the subscriber.status- The subscription status of the subscriber.created_at- Timestamp when the subscriber was created.updated_at- Timestamp when the subscriber was last updated.
Dependencies
- Listmonk service API with authentication credentials
Troubleshooting
- Ensure the subscriber identifier matches the chosen identification method (ID or email).
- Verify that the subscriber ID or email exists in the Listmonk service to avoid 'not found' errors.
- Check network connectivity and proxy settings if requests fail.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option cautiously.