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 retrieve detailed information about a specific subscriber within a mailing list. It is particularly useful for marketing automation workflows where you need to fetch subscriber data such as subscription status, profile details, or engagement metrics.
A common scenario includes verifying subscriber details before sending targeted campaigns or updating subscriber records in other systems based on their current status.
For example, you can use this node to get the details of a subscriber by providing the mailing list ID and the subscriber's email address, then use that data to personalize follow-up emails or segment your audience dynamically.
Properties
| Name | Meaning |
|---|---|
| List Id | The identifier of the mailing list from which to retrieve the subscriber details. Must be a number. |
| Subscriber | The email address of the subscriber whose details you want to fetch. |
Output
The node outputs JSON data containing the subscriber's details as returned by the Acumbamail API. This typically includes fields such as subscriber status, subscription date, custom fields, and any other metadata associated with the subscriber in the specified list.
If the API supports it, binary data output is not expected for this operation since it deals with subscriber information retrieval.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node uses the base URL
https://acumbamail.com/api/1for API requests. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an incorrect list ID or subscriber email may result in "subscriber not found" errors.
- Network connectivity problems can lead to request timeouts or failures.
Error messages:
- 401 Unauthorized: Check that the API key credential is correctly set up and has the required permissions.
- 404 Not Found: Verify that the list ID and subscriber email are correct and exist in your Acumbamail account.
- 400 Bad Request: Ensure that all required parameters (list ID and subscriber email) are provided and valid.
Resolving these usually involves verifying credentials, input values, and network access.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and response formats)
- n8n documentation on API Credentials