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 information about email campaigns, specifically focusing on obtaining the list of soft bounces for a given campaign. Soft bounces typically indicate temporary delivery issues such as a full mailbox or a temporary server problem. This node is useful for email marketers and campaign managers who want to monitor and analyze the deliverability of their campaigns by identifying recipients who did not receive emails due to transient issues.
A practical example use case is when a user wants to review which contacts experienced soft bounces in a recent campaign to decide whether to retry sending or clean the mailing list.
Properties
| Name | Meaning |
|---|---|
| Campaign Id | Identifier of the campaign to retrieve soft bounce information for. Must be provided as a number. |
Output
The node outputs JSON data containing details about the soft bounces related to the specified campaign. The exact structure depends on the Acumbamail API response but generally includes information such as the email addresses that soft bounced, timestamps, and possibly reasons for the bounce.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail API.
- The node uses the base URL
https://acumbamail.com/api/1for API requests. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Invalid Campaign Id: If the campaign ID does not exist or is incorrect, the API may return an error or empty results. 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 set up.
- Network Issues: Connectivity problems can prevent the node from reaching the Acumbamail API. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests might lead to rate limiting by the Acumbamail service. Implement retries or backoff strategies if needed.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and response formats)
- n8n Documentation on Creating Custom Nodes