Actions9
- List Actions
- Subscriber Actions
- Transactional Message Actions
Overview
The node interacts with the Listmonk service, specifically allowing management of mailing lists. For the "List" resource and "Delete" operation, it deletes a specified mailing list by its ID. This is useful for automating cleanup or management of mailing lists within marketing or communication workflows.
Practical examples:
- Automatically removing outdated or unused mailing lists.
- Integrating list deletion as part of a larger campaign lifecycle automation.
- Cleaning up test or temporary lists after data processing.
Properties
| Name | Meaning |
|---|---|
| List ID | ID of the list to delete |
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. The exact structure depends on the Listmonk API response but generally includes status information.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Listmonk service.
- Needs the Listmonk service URL configured in credentials.
- The node sends HTTP requests to the Listmonk API endpoint
/api.
Troubleshooting
Common issues:
- Invalid or missing List ID: The node requires a valid numeric List ID; ensure this is provided.
- Authentication errors: Verify that the API key and host URL are correctly set in credentials.
- Network or connectivity problems: Ensure the Listmonk service is reachable from n8n.
Error messages:
- Unauthorized or 401 errors indicate invalid API credentials.
- 404 errors may mean the specified List ID does not exist.
- 400 errors could indicate malformed requests, such as invalid List ID format.
Resolving these typically involves verifying input parameters and credential configurations.
Links and References
- Listmonk API Documentation (for detailed API endpoints and responses)