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 is designed to retrieve subscriber information from a mailing list service. Specifically, the "Get Subscribers" operation under the "Subscribers" resource fetches subscribers belonging to a specified list. This node is useful for scenarios where you want to analyze, segment, or export subscriber data from a particular mailing list.
Practical examples include:
- Exporting active subscribers for targeted email campaigns.
- Retrieving unsubscribed or bounced users to clean your mailing lists.
- Fetching detailed subscriber data for reporting or integration with CRM systems.
Properties
| Name | Meaning |
|---|---|
| List Id | The identifier of the mailing list from which to retrieve subscribers. This is a required numeric value. |
| Additional Query Parameters | Optional parameters to refine the subscriber retrieval: - Status: Filter subscribers by status: 0: active 1: non-verified 2: unsubscribed 3: hard bounced 4: complained - Block Index: Pagination index for results in blocks of 10,000 subscribers (default 0). - All Fields: Whether to return all fields of each subscriber (default 0). - Complete Json: Whether to return a complete JSON response (default 0). |
Output
The node outputs JSON data containing the list of subscribers retrieved based on the input parameters. The structure typically includes subscriber details such as email, status, and other metadata depending on the query parameters used (e.g., all fields or complete JSON).
If binary data were involved (not indicated here), it would represent attachments or files related to subscribers, but this node focuses on JSON subscriber data only.
Dependencies
- Requires an API key credential for authenticating requests to the mailing list service's API.
- The base URL for API requests is
https://acumbamail.com/api/1. - The node expects JSON responses and sends requests with appropriate headers (
AcceptandContent-Typeset toapplication/json).
Troubleshooting
- Missing or invalid List Id: Since the List Id is required, ensure it is provided and valid. Errors may occur if the list does not exist or the ID is incorrect.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limiting or large result sets: When retrieving many subscribers, use the Block Index parameter to paginate through results to avoid timeouts or limits.
- Invalid status values: Use only the defined status codes (0-4) to filter subscribers; otherwise, the API may reject the request.
- Unexpected response format: If using
complete_jsonorall_fields, be prepared to handle more complex JSON structures.
Links and References
- Acumbamail API Documentation (for detailed API usage and parameter descriptions)
- n8n documentation on creating custom nodes