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, specifically allowing you to unsubscribe a subscriber from a mailing list. It is useful in scenarios where you want to automate the removal of email addresses from your marketing or notification lists based on certain triggers or workflows within n8n.
For example, you might use this node to automatically unsubscribe users who request it via a form submission or when their subscription status changes in another system.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to include in the unsubscribe request body. Options: |
| - List Id | Numeric identifier of the mailing list from which to unsubscribe the subscriber. |
| Email address of the subscriber to be unsubscribed. |
These properties allow you to specify the subscriber's email and the list they should be removed from. Both are sent as part of the request body to the API.
Output
The node outputs JSON data representing the response from the Acumbamail API after attempting to unsubscribe the subscriber. This typically includes confirmation of the unsubscription or error details if the operation failed.
No binary data output is involved.
Dependencies
- Requires an API key credential for Acumbamail to authenticate requests.
- The node uses the Acumbamail API endpoint at
https://acumbamail.com/api/1. - Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Missing or incorrect API credentials will cause authentication failures.
- Providing an invalid or non-existent list ID or email may result in errors or no action taken.
- Network connectivity problems can prevent the node from reaching the Acumbamail API.
Error messages:
- Authentication errors usually indicate invalid or missing API keys; verify and update credentials.
- Validation errors from the API may indicate missing required fields like email or list ID; ensure these are correctly set.
- Timeout or network errors suggest connectivity issues; check your internet connection and firewall settings.
Links and References
- Acumbamail API Documentation (for detailed API usage and parameters)
- n8n Documentation (for general guidance on using and configuring nodes)