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 integrates with the Acumbamail API to retrieve campaign data. Specifically, the "Get Campaigns" operation fetches a list of campaigns from the user's Acumbamail account. This is useful for scenarios where users want to automate reporting, synchronize campaign data with other systems, or trigger workflows based on campaign statuses.
For example, a marketing team could use this node to automatically pull the latest campaign details into a dashboard or CRM system, enabling real-time insights and follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Complete Json | When set to 1, returns the full detailed JSON response of campaigns; default is 0 (partial). |
Output
The node outputs JSON data representing the campaigns retrieved from Acumbamail. The structure corresponds to the API's response format for campaigns. If the "Complete Json" property is enabled, the output includes the entire detailed JSON object for each campaign, otherwise it may be a simplified version.
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 token in n8n credentials is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Empty or incomplete data: Verify the "Complete Json" property setting; enabling it returns more comprehensive data.
- Network issues: Confirm that the n8n instance can reach the Acumbamail API endpoint without firewall restrictions.
- API rate limits: Be aware of any rate limiting imposed by Acumbamail which might cause request failures.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and response formats)
- n8n documentation on creating custom nodes