Actions71
- Settings Actions
- Subscribers Actions
- Create Subscriber
- Manage Subscriber Lists By Query
- Get Subscribers
- Delete Subscriber By List
- Get Subscriber By Id
- Update Subscriber By Id
- Delete Subscriber By Id
- Manage Subscriber Lists
- Manage Subscriber List By Id
- Manage Blocklist By Subscriber List
- Manage Blocklist Subscribers By Id
- Export Subscriber Data By ID
- Get Subscriber Bounces By Id
- Delete Subscriber Bounces By Id
- Subscriber Send Optin By Id
- Delete Subscriber By Query
- Blocklist Subscribers Query
- Bounces Actions
- Import Actions
- Campaigns Actions
- Update Preview Campaign By Id
- Get Campaigns
- Create Campaign
- Get Campaign By Id
- Update Campaign By Id
- Delete Campaign By Id
- Get Running Campaign Stats
- Get Campaign Analytics
- Preview Campaign By Id
- Preview Campaign Text By Id
- Update Campaign Status By Id
- Update Campaign Archive By Id
- Create Campaign Content By Id
- Test Campaign By Id
- Media Actions
- Templates Actions
- Public Actions
- Miscellaneous Actions
- Admin Actions
- Logs Actions
- Lists Actions
- Transactional Actions
- Maintenance Actions
Overview
This node interacts with the Listmonk API to perform maintenance operations, specifically to delete unconfirmed subscriptions. It is useful for cleaning up subscription lists by removing entries that have not been confirmed, helping maintain a clean and accurate subscriber database.
Use Case Examples
- A marketing team uses this node to automatically delete unconfirmed email subscriptions from their mailing list to ensure only engaged users receive campaigns.
- An administrator schedules this node to run periodically to remove unconfirmed subscriptions, reducing clutter and potential spam issues.
Properties
| Name | Meaning |
|---|---|
| Request Options | Settings to control request behavior such as batching, SSL certificate validation, proxy usage, and timeout. |
Output
JSON
success- Indicates whether the deletion of unconfirmed subscriptions was successful.deletedCount- Number of unconfirmed subscriptions that were deleted.message- Additional information or status message from the API response.
Dependencies
- Requires an API key credential for authenticating with the Listmonk API.
Troubleshooting
- If the node fails due to SSL certificate issues, enable 'Ignore SSL Issues' to bypass validation (not recommended for production).
- Ensure the API base URL and credentials are correctly configured to avoid authentication errors.
- Batching settings should be adjusted based on API rate limits to prevent request throttling or failures.
- Timeout should be set sufficiently high to allow the server to respond, especially for large batch operations.
Links
- Listmonk API Documentation - Official documentation for the Listmonk API, including endpoints and usage details.