Actions71
- Settings Actions
- Subscribers Actions
- Create Subscriber
- Manage Subscriber Lists By Query
- Get Subscribers
- Delete Subscriber By List
- Get Subscriber By Id
- Update Subscriber By Id
- Delete Subscriber By Id
- Manage Subscriber Lists
- Manage Subscriber List By Id
- Manage Blocklist By Subscriber List
- Manage Blocklist Subscribers By Id
- Export Subscriber Data By ID
- Get Subscriber Bounces By Id
- Delete Subscriber Bounces By Id
- Subscriber Send Optin By Id
- Delete Subscriber By Query
- Blocklist Subscribers Query
- Bounces Actions
- Import Actions
- Campaigns Actions
- Update Preview Campaign By Id
- Get Campaigns
- Create Campaign
- Get Campaign By Id
- Update Campaign By Id
- Delete Campaign By Id
- Get Running Campaign Stats
- Get Campaign Analytics
- Preview Campaign By Id
- Preview Campaign Text By Id
- Update Campaign Status By Id
- Update Campaign Archive By Id
- Create Campaign Content By Id
- Test Campaign By Id
- Media Actions
- Templates Actions
- Public Actions
- Miscellaneous Actions
- Admin Actions
- Logs Actions
- Lists Actions
- Transactional Actions
- Maintenance Actions
Overview
This node operation retrieves bounce information for a specific subscriber by their ID from the Listmonk API. It is useful for scenarios where you need to analyze or manage email bounces related to individual subscribers, such as cleaning up mailing lists or investigating delivery issues.
Use Case Examples
- Get bounce details for a subscriber to understand why their emails are not being delivered.
- Fetch bounce data to update subscriber status or trigger follow-up actions in an email marketing workflow.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the subscriber whose bounce information is to be retrieved. |
| Request Options | Additional options to customize the API request, including batching, SSL certificate validation, proxy settings, and request timeout. |
Output
JSON
bounceDetails- Contains the bounce information retrieved for the specified subscriber ID.
Dependencies
- Requires an API key credential for authenticating with the Listmonk API.
Troubleshooting
- Ensure the subscriber ID provided is valid and exists in the Listmonk system to avoid 'not found' errors.
- Check network connectivity and proxy settings if requests time out or fail to reach the API.
- If SSL certificate validation errors occur, consider enabling the option to ignore SSL issues, but be aware of the security implications.
Links
- Listmonk API Documentation - Official documentation for the Listmonk API, including endpoints for managing subscribers and bounces.