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
The node integrates with the Acumbamail API to batch add subscribers to a mailing list. It allows users to submit multiple subscriber details at once, including custom merge fields and optional parameters such as double opt-in confirmation emails and updating existing subscribers. This node is useful for marketing automation workflows where bulk subscriber management is needed, such as importing contacts from other systems or syncing subscriber data.
Practical examples:
- Importing a CSV list of email addresses with personalized merge tags into an Acumbamail mailing list.
- Adding new subscribers while sending them a confirmation email (double opt-in).
- Updating existing subscriber information if they are already on the list.
Properties
| Name | Meaning |
|---|---|
| Merge Fields | A JSON dictionary containing merge tags as keys and their corresponding values for each subscriber. |
| Additional Body Fields | Optional settings: • Double Optin: 0 or 1 to activate sending confirmation email. • Update Subscriber: 0 or 1 to modify existing subscriber fields. • Complete Json: 0 or 1 to return a complete JSON response with email and ID. |
Output
The node outputs JSON data representing the result of the batch add operation. If the "Complete Json" option is enabled, the output includes detailed subscriber information in the format:
{
"email": "email@domain.com",
"id": 555
}
Otherwise, it returns a simpler response indicating success or failure per subscriber.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node uses the Acumbamail REST API endpoint
https://acumbamail.com/api/1. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
- Common issues:
- Invalid or missing API key leading to authentication errors.
- Malformed JSON in the "Merge Fields" property causing parsing failures.
- Attempting to update subscribers without enabling the "Update Subscriber" option may cause conflicts.
- Error messages:
- Authentication errors typically indicate invalid credentials; verify and re-enter the API key.
- JSON parse errors suggest incorrect formatting in the merge fields input; ensure valid JSON syntax.
- API rate limits or network errors may occur; retry after some time or check network connectivity.
Links and References
- Acumbamail API Documentation (for detailed API usage and parameters)
- n8n documentation on Creating Custom Nodes