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 basic information about a specific email campaign. It is useful for users who want to fetch details such as campaign status, name, or other metadata without manually querying the API. Typical use cases include automating reporting workflows, monitoring campaign performance, or integrating campaign data into other systems.
For example, a marketing automation workflow could use this node to get the current status of a campaign by its ID and then trigger follow-up actions based on that status.
Properties
| Name | Meaning |
|---|---|
| Campaign Id | The unique numeric identifier of the campaign whose basic information you want to retrieve. This is a required field. |
Output
The node outputs JSON data containing the basic information of the specified campaign as returned by the Acumbamail API. This typically includes fields such as campaign name, status, creation date, and other metadata relevant to the campaign.
If the API supports binary data in responses (not evident from the provided code), it would be included accordingly, but here the output is primarily JSON.
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. - The request headers specify JSON content type and acceptance.
- No additional external dependencies are indicated beyond the Acumbamail API and the n8n environment.
Troubleshooting
- Missing or invalid Campaign Id: Since the campaign ID is required, omitting it or providing an invalid number will likely cause the API call to fail. Ensure the campaign ID is correct and exists in your Acumbamail account.
- Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate. Verify that the API key is valid and properly configured in n8n credentials.
- API connectivity issues: Network problems or changes in the Acumbamail API endpoint may cause failures. Check network access and confirm the API base URL has not changed.
- Unexpected API response: If the API returns an error or unexpected data structure, review the campaign ID and API documentation to ensure compatibility.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general usage of custom nodes and credentials)