Listmonk icon

Listmonk

Interact with Listmonk API

Actions71

Overview

This node interacts with the Listmonk API to retrieve bounce records related to email campaigns. It is useful for monitoring and managing email bounces, which helps in maintaining a clean mailing list and improving email deliverability. For example, a marketing team can use this node to fetch bounce data for a specific campaign to analyze why emails were not delivered successfully.

Use Case Examples

  1. Retrieve bounce records for a specific campaign by providing the campaign ID.
  2. Paginate through bounce records by specifying the page number and items per page.
  3. Filter bounce records by their source or sort them by email, campaign name, source, or creation date.

Properties

Name Meaning
Campaign Id Numeric identifier for retrieving bounce records associated with a specific campaign.
Page Page number for paginated results, starting from 1 for the first page.
Per Page Number of items per page; can be an integer for specific page size or 'all' to retrieve all results.
Source Filter bounce records by their source of origin.
Order By Field by which to sort the bounce records.
Order Sort order of results, either ascending or descending.

Output

JSON

  • bounces - Array of bounce records retrieved from the API, each containing details about the bounced email, campaign, source, and timestamp.

Dependencies

  • Requires an API key credential for authenticating with the Listmonk API.

Troubleshooting

  • Ensure the API base URL and credentials are correctly configured to avoid authentication errors.
  • If pagination parameters are incorrect, the node may return empty or incomplete results; verify 'page' and 'per_page' values.
  • SSL certificate validation issues can be bypassed by enabling the 'Ignore SSL Issues' option, but this should be used cautiously.
  • Proxy settings must be correctly specified if a proxy is required for network access.

Links

  • Listmonk API Documentation - Official documentation for the Listmonk API, detailing endpoints and parameters including bounce retrieval.

Discussion