Listmonk icon

Listmonk

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

Actions32

Template → Get Template by ID

AI-generated

Overview

The node integrates with a listmonk instance, a self-hosted newsletter and email marketing platform. Specifically, the "Get Template by ID" operation retrieves detailed information about an email template stored in listmonk using its unique numeric identifier. This is useful when you want to fetch the content or metadata of a specific email template for previewing, editing, or sending campaigns.

Practical examples include:

  • Fetching a template's HTML content to display it in a custom UI.
  • Retrieving template details before updating or duplicating it.
  • Using the template data as part of an automated workflow that sends personalized emails.

Properties

Name Meaning
ID The unique numeric identifier of the template to retrieve. Must be a valid number corresponding to an existing template in listmonk.

Output

The output JSON contains the full details of the requested template. This typically includes fields such as the template's ID, name, subject, body (HTML or text), creation date, and other metadata relevant to the template configuration in listmonk.

If the node supports binary data output (not explicitly shown here), it would likely represent attachments or media related to the template, but this operation primarily returns JSON data describing the template.

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 listmonk API to be accessible at the configured base URL under /api.

Troubleshooting

  • Invalid ID error: If the provided ID does not correspond to any template, the API will return an error. Ensure the ID is correct and the template exists.
  • Authentication errors: Incorrect or missing credentials will cause authorization failures. Verify the API credentials are correctly set up in n8n.
  • Network issues: If the listmonk server is unreachable, check network connectivity and the correctness of the domain URL.
  • API changes: If listmonk updates their API, some fields or endpoints might change, causing unexpected errors. Keep the node and listmonk version compatible.

Links and References

Discussion