Listmonk icon

Listmonk

Interact with a listmonk instance for email marketing and newsletter management. Supports creating subscribers, managing campaigns, sending emails, and more.

Actions32

Subscriber → Delete Subscriber by ID

AI-generated

Overview

This node integrates with a Listmonk instance, an email marketing and newsletter management platform. Specifically, the "Delete Subscriber by ID" operation allows users to remove a subscriber from their mailing list by specifying the subscriber's unique numeric ID. This is useful for managing subscriber lists by cleaning out inactive or unwanted contacts, ensuring compliance with data privacy regulations, or simply maintaining an up-to-date mailing list.

Practical examples include:

  • Automatically removing unsubscribed users from your mailing list.
  • Deleting test subscribers after campaign trials.
  • Cleaning up duplicate or invalid subscriber entries.

Properties

Name Meaning
ID The unique identifier of the subscriber to delete. Must be a valid number representing the subscriber's ID in the Listmonk system.

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. There is no binary output associated with this operation.

Dependencies

  • Requires connection to a Listmonk instance via its 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 expects the API to accept and return JSON-formatted data.

Troubleshooting

  • Invalid ID Error: If the provided ID is not a valid number or does not correspond to an existing subscriber, the API may return an error indicating the subscriber was not found. Ensure the ID is correct and exists in the Listmonk database.
  • Authentication Failures: Incorrect or missing credentials (domain, username, password) will cause authentication errors. Verify that the API credentials are correctly configured.
  • Network Issues: Connectivity problems between n8n and the Listmonk server can cause request failures. Check network access and firewall settings.
  • API Endpoint Errors: If the Listmonk instance URL is incorrect or the API endpoint has changed, the node will fail to communicate properly. Confirm the domain URL and API version compatibility.

Links and References

Discussion