Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
This node integrates with a list management system called Listmonk, allowing users to perform various operations on lists, campaigns, media, templates, and subscribers. Specifically, the "Delete Template by ID" operation under the "Template" resource enables users to delete a template from their Listmonk instance by specifying its unique identifier.
Common scenarios for this operation include:
- Removing outdated or unused email templates from your marketing system.
- Cleaning up templates that are no longer relevant to current campaigns.
- Automating template lifecycle management as part of a larger workflow.
For example, a user might automate the deletion of a template after a campaign ends to keep their template library organized.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the template to delete. This is a required string property. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Listmonk instance via API.
- Needs an API authentication credential consisting of a domain URL, username, and password.
- The base URL for API requests is constructed from the provided domain credential.
- The node sends authenticated HTTP requests with JSON payloads.
Troubleshooting
- Invalid or missing ID: If the ID property is empty or incorrect, the API will likely return an error indicating the template was not found. Ensure the ID corresponds to an existing template.
- Authentication errors: Incorrect credentials (domain, username, or password) will cause authentication failures. Verify the API credentials are correct and have sufficient permissions.
- Network issues: Connectivity problems to the Listmonk server can cause request failures. Check network access and firewall settings.
- API endpoint changes: If the Listmonk API version changes or the endpoint structure is updated, the node may fail. Keep the node and API versions compatible.