Actions42
- Campaigns Actions
- Create Campaign
- Create Template
- Duplicate Template
- Get Campaign Basic Information
- Get Campaign Clicks
- Get Campaigns
- Get Campaign Information By ISP
- Get Campaign Links
- Get Campaign Openers
- Get Campaign Openers By Browser
- Get Campaign Openers By Countries
- Get Campaign Openers By Os
- Get Campaign Soft Bounces
- Get Campaign Total Information
- Get Stats By Date
- Send Template Campaign
- Subscribers Actions
- SMS Actions
- SMTP Actions
- Webhooks Actions
Overview
This node integrates with the Acumbamail API to manage subscribers within mailing lists. Specifically, the "Delete Subscriber Post" operation under the "Subscribers" resource allows users to delete a subscriber from a specified mailing list by providing the list identifier and the subscriber's email address.
Common scenarios for this node include:
- Removing unsubscribed or inactive users from mailing lists.
- Cleaning up mailing lists by deleting specific subscribers.
- Automating subscriber management workflows where deletion is required based on external triggers.
For example, after detecting a bounced email or a user request to unsubscribe, this node can be used to remove that subscriber from the relevant list automatically.
Properties
| Name | Meaning |
|---|---|
| List Id | The numeric identifier of the mailing list from which the subscriber will be deleted. |
| The email address of the subscriber to delete from the specified list. |
Output
The node outputs JSON data representing the response from the Acumbamail API after attempting to delete the subscriber. This typically includes confirmation of deletion or error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node sends HTTP requests to the Acumbamail API endpoint at
https://acumbamail.com/api/1. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
- Invalid List Id or Email: If the provided list ID or email does not exist or is incorrect, the API may return an error indicating the subscriber was not found. Verify the inputs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Network Issues: Connectivity problems to the Acumbamail API endpoint can cause timeouts or request failures. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests might trigger rate limiting by Acumbamail. Implement retry logic or reduce request frequency as needed.
Links and References
- Acumbamail API Documentation (for detailed API usage and error codes)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)