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 interacts with the Acumbamail API to retrieve detailed information about a specific email campaign filtered by Internet Service Provider (ISP). It is useful for marketers and analysts who want to analyze campaign performance or status segmented by ISP, enabling targeted insights and optimization of email marketing efforts.
A practical example would be fetching delivery and engagement statistics for a particular campaign to understand how different ISPs are handling the emails, which can help in troubleshooting deliverability issues or tailoring future campaigns.
Properties
| Name | Meaning |
|---|---|
| Campaign Id | Identifier of the campaign that you want to retrieve information about. This is a required numeric value. |
Output
The node outputs JSON data containing detailed information about the specified campaign as returned by the Acumbamail API. The structure typically includes campaign metadata, status, and ISP-specific metrics or statistics relevant to the campaign's performance.
If the API supports binary data (e.g., attachments or reports), the node would handle it accordingly, but based on the provided code and context, the output focuses on JSON-formatted campaign information.
Dependencies
- Requires an API key credential for authenticating requests to the Acumbamail service.
- The node depends on the Acumbamail REST API endpoint at
https://acumbamail.com/api/1. - Uses the
@avantguardllc/n8n-openapi-nodepackage for building request properties from the OpenAPI specification.
Troubleshooting
- Invalid Campaign Id: If the campaign ID does not exist or is incorrect, the API may return an error or empty response. Verify the campaign ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly configured in n8n.
- Network Issues: Connectivity problems to the Acumbamail API endpoint can cause timeouts or errors. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests might trigger rate limiting by Acumbamail. Implement retries or backoff strategies if needed.
Links and References
- Acumbamail API Documentation (general reference for API endpoints and parameters)
- n8n Documentation for configuring credentials and using HTTP-based nodes