Listmonk icon

Listmonk

Interact with a listmonk instance for email marketing and newsletter management. Supports creating subscribers, managing campaigns, sending emails, and more.

Actions32

Campaign → Get by ID

AI-generated

Overview

The node integrates with a listmonk instance, a platform for email marketing and newsletter management. Specifically, the "Campaign" resource with the "Get by ID" operation allows users to retrieve detailed information about a single campaign by specifying its unique numeric ID. This is useful when you want to fetch the current status, content, or metadata of a particular campaign for reporting, auditing, or further processing within an automation workflow.

Practical examples include:

  • Automatically fetching campaign details after creation to log or analyze performance.
  • Retrieving campaign data to customize follow-up actions based on campaign attributes.
  • Integrating campaign info into dashboards or CRM systems.

Properties

Name Meaning
ID The unique identifier of the campaign to retrieve. Must be a valid number representing the campaign's ID in the listmonk system.

Output

The output JSON contains the detailed data of the requested campaign. This typically includes fields such as campaign name, subject, content, status, scheduling information, and statistics related to the campaign's performance (e.g., sent count, open rate). The exact structure depends on the listmonk API response for a campaign object.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to a listmonk instance via its API.
  • Needs credentials including domain URL, username, and password for basic authentication.
  • The node expects the base URL to be configured without trailing slashes; it appends /api automatically.
  • Proper permissions on the listmonk API to read campaign data.

Troubleshooting

  • Invalid ID error: If the provided ID is not a valid number or does not correspond to an existing campaign, the node will likely return an error indicating the campaign was not found. Verify the ID value before execution.
  • Authentication failures: Incorrect or missing credentials will cause authorization errors. Ensure the API user and password are correct and have sufficient rights.
  • Network issues: Connectivity problems to the listmonk server will result in request timeouts or connection errors. Check network access and endpoint availability.
  • API changes: If the listmonk API version changes, some fields or endpoints might differ, causing unexpected errors. Confirm compatibility with the installed listmonk version.

Links and References

Discussion