Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
This node integrates with a listmonk instance, a self-hosted newsletter and mailing list manager. Specifically, the "Delete Media by ID" operation under the "Media" resource allows users to delete a media object from their listmonk server by specifying its unique identifier. This is useful for managing and cleaning up media assets such as images or files that are no longer needed in campaigns or templates.
Common scenarios include:
- Removing outdated or incorrect media files from the system.
- Automating cleanup of unused media after campaign completion.
- Managing storage by deleting large media items no longer referenced.
Example: A user wants to delete an image previously uploaded to listmonk to free up space or remove it from future campaigns. They provide the media ID, and this node deletes it via the API.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the media object to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will be a confirmation response from the listmonk API indicating whether the deletion was successful. The exact structure depends on the API but usually includes status information.
No binary data output is expected from this operation.
Dependencies
- Requires connection to a listmonk instance with valid credentials (username and password).
- Needs the base URL of the listmonk API endpoint configured.
- The node uses basic HTTP authentication with these credentials.
- The environment must allow outbound HTTP requests to the listmonk server.
Troubleshooting
- Invalid ID error: If the provided media ID does not exist, the API may return an error indicating the media was not found. Verify the ID is correct.
- Authentication failure: Incorrect username or password will cause authorization errors. Ensure credentials are accurate.
- Network issues: Failure to reach the listmonk server could be due to network problems or incorrect base URL configuration.
- Permission denied: The authenticated user might lack permissions to delete media. Check user roles and API access rights.
- Unexpected API response: If the API changes or returns unexpected data, the node might fail. Confirm compatibility with your listmonk version.
Links and References
- listmonk Official Documentation
- listmonk API Reference (for details on media endpoints)