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 allows sending a pre-designed email campaign template to specified mailing lists or segments. It is useful for automating email marketing workflows where you want to trigger the dispatch of a templated campaign programmatically, such as after a user signs up, completes a purchase, or on scheduled intervals.
Typical use cases include:
- Sending promotional campaigns using predefined templates.
- Triggering transactional or informational emails based on events.
- Managing segmented email distributions by specifying lists or segments.
Properties
| Name | Meaning |
|---|---|
| Name | The internal name of the campaign (not visible to recipients). |
| From Name | The sender's name that will appear in the recipient's inbox. |
| From Email | The email address from which the campaign will be sent. |
| Subject | The subject line of the email campaign. |
| Template Id | The identifier of the email template to send. |
| Lists | JSON object specifying the identifiers of the lists or segments to send the campaign to. Segments are prefixed with 's'. You cannot send to multiple segments of the same list or mix a segment and its parent list. |
| Https | Numeric flag (usually 0 or 1) to enable HTTPS protocol for tracking links within the campaign. Default is 0 (disabled). |
Output
The node outputs JSON data representing the response from the API after attempting to send the campaign. This typically includes status information about the campaign dispatch request, such as success confirmation or error details.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node uses the Acumbamail API endpoint at
https://acumbamail.com/api/1. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
- Invalid Template Id: If the provided template ID does not exist or is incorrect, the API may return an error. Verify the template ID before sending.
- List/Segment Conflicts: Sending to multiple segments of the same list or mixing a segment and its parent list is disallowed. Ensure the
listsproperty respects this constraint. - Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm the API key is correctly configured.
- Invalid Email Format: The "From Email" must be a valid email address; otherwise, the API may reject the request.
- HTTPS Flag Misuse: The
httpsproperty should be 0 or 1. Using other values might lead to unexpected behavior.
Links and References
- Acumbamail API Documentation (for detailed API usage and campaign management)
- n8n Documentation (for general guidance on using custom nodes and credentials)