Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Template → Modify
AI-generatedOverview
The node integrates with a Listmonk instance, a self-hosted newsletter and email marketing platform. Specifically, the "Template" resource with the "Modify" operation allows users to update existing email templates used in campaigns or transactional emails. This is useful for maintaining and updating email content dynamically without manually editing templates in the Listmonk UI.
Common scenarios include:
- Updating the subject line or body of an email template before sending a campaign.
- Changing the type of the template between campaign and transactional.
- Renaming templates to better organize them.
Practical example: A marketing team wants to quickly update the promotional message in their campaign template to reflect a new discount offer. Using this node, they can modify the template's body and subject directly from an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the template. Used to identify the template within Listmonk. |
| Subject | The email subject line for the template. |
| Type | The type of the template. Options are: "Campaign" (for marketing campaigns) or "Transactional" (for automated emails). |
| Body | The main content/body of the email template. Supports code editing for HTML or text. |
| ID | The unique numeric identifier of the template to be modified. Must be a valid number. |
Output
The node outputs JSON data representing the updated template object as returned by the Listmonk API after modification. This typically includes fields such as the template's ID, name, subject, type, body, and metadata about the update status.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the template, but this is not applicable for the Modify Template operation.
Dependencies
- Requires connection to a Listmonk instance with API access.
- Needs credentials including domain URL, username, and password for authentication.
- The node uses the Listmonk REST API under the
/apipath. - Proper permissions on the Listmonk server to modify templates.
Troubleshooting
- Invalid ID error: Ensure the template ID provided exists and is a valid number.
- Authentication failures: Verify that the API credentials (domain, username, password) are correct and have sufficient rights.
- Empty or malformed body: The template body should be valid HTML or plain text; invalid content might cause errors.
- Network issues: Confirm the Listmonk server is reachable from n8n and the base URL is correctly configured without trailing slashes.
- API rate limits or server errors: Check Listmonk server logs if modifications fail unexpectedly.
Links and References
- Listmonk Official Documentation
- Listmonk API Reference
- n8n Documentation on HTTP Request Node (for understanding API calls)