Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
The node "Listmonk" allows interaction with a Listmonk instance, which is an open-source self-hosted newsletter and mailing list manager. Specifically, the "Get by ID" operation under the "Campaign" resource retrieves detailed information about a single campaign using its unique identifier.
This operation is useful when you want to fetch the full details of a specific email campaign, for example, to display its content, check its status, or analyze its metadata before performing further actions such as updates or sending previews.
Practical examples:
- Fetching a campaign's data to show in a dashboard.
- Retrieving campaign details before updating or deleting it.
- Getting campaign stats or preview based on the campaign ID.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the campaign object to retrieve. This is a required string input. |
Output
The output JSON will contain the detailed data of the requested campaign identified by the provided ID. This typically includes fields such as campaign name, subject, content, status, creation date, and other metadata related to the campaign.
If the node supports binary data output (not explicitly shown here), it would generally represent attachments or media associated with the campaign, but this is not indicated in the provided code snippet.
Dependencies
- Requires connection to a Listmonk instance via its API.
- Needs credentials including domain URL, username, and password for basic authentication.
- The base URL for API requests is constructed from the provided domain credential.
- The node expects the Listmonk API to be accessible and properly configured.
Troubleshooting
- Invalid or missing ID: If the ID property is empty or incorrect, the API call will fail. Ensure the ID corresponds to an existing campaign.
- Authentication errors: Incorrect username/password or domain URL will cause authorization failures. Verify credentials and endpoint.
- Network issues: If the Listmonk server is unreachable, the node will error out. Check network connectivity and server status.
- API changes: If the Listmonk API version changes, some fields or endpoints might differ, causing unexpected errors.
Common error messages may include:
- "Unauthorized" or "Authentication failed": Check API credentials.
- "Not Found": The campaign ID does not exist.
- "Network Error": Unable to reach the Listmonk server.