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 detailed reports about SMS subscribers for a specific SMS campaign. It is useful in marketing automation workflows where users want to analyze subscriber engagement or campaign performance by fetching subscriber data related to an SMS campaign.
A practical example would be a marketing team automating the retrieval of SMS campaign subscriber reports after sending out a campaign, enabling them to process or visualize subscriber responses and metrics within their workflow.
Properties
| Name | Meaning |
|---|---|
| Sms Campaign Id | Identifier of the SMS campaign for which the subscriber report should be retrieved. This is a required numeric value representing the campaign ID. |
Output
The node outputs JSON data containing the subscriber report for the specified SMS campaign. The structure typically includes details about each subscriber's interaction or status related to that campaign (e.g., delivery status, timestamps, subscriber identifiers). No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node makes HTTP requests to the Acumbamail API endpoint at
https://acumbamail.com/api/1. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Missing or invalid campaign ID: If the "Sms Campaign Id" property is not provided or invalid, the API call will fail. Ensure this field is correctly set.
- Authentication errors: If the API key credential is missing or incorrect, the node will return authorization errors. Verify the API key and its permissions.
- Network or API downtime: Connectivity issues or Acumbamail service outages can cause request failures. Check network connectivity and Acumbamail service status.
- Unexpected response format: If the API changes its response schema, the node might not parse the output correctly. Review API documentation for updates.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)