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 create or update email campaign templates. Specifically, the "Create Template" operation under the "Campaigns" resource allows users to define a new email template by specifying its name and HTML content. This is useful for automating the management of email templates within marketing workflows, enabling dynamic creation or updating of templates without manual intervention.
Practical examples include:
- Automatically generating personalized email templates based on user data.
- Updating existing templates programmatically as part of a CI/CD pipeline for marketing assets.
- Creating multiple templates in bulk from external data sources.
Properties
| Name | Meaning |
|---|---|
| Template Name | The name of the email template to create. This is required and identifies the template. |
| Html Content | The HTML markup that defines the visual content of the template. Required field. |
| Additional Body Fields | Optional additional fields to customize the template: |
| - Id | Numeric identifier of an existing template to update instead of creating a new one. |
| - Custom Category | A category name to assign the template to, for organizational purposes. |
| - Subject | The subject line associated with the template, used when sending emails. |
| - Bee Json | A JSON object describing the template contents in a structured format (likely for a specific editor). |
Output
The node outputs JSON data representing the response from the Acumbamail API after creating or updating the template. This typically includes details such as the template ID, status, and any metadata returned by the API. There is no indication of binary output in this operation.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail service.
- The node uses the Acumbamail REST API endpoint at
https://acumbamail.com/api/1. - Proper configuration of the API key credential in n8n is necessary for successful requests.
Troubleshooting
- Missing Required Fields: If "Template Name" or "Html Content" are not provided, the API will likely reject the request. Ensure these fields are filled.
- Invalid JSON in Bee Json: The "Bee Json" field expects valid JSON; malformed input may cause errors.
- API Authentication Errors: Incorrect or missing API credentials will result in authentication failures.
- Updating Nonexistent Template: Providing an invalid template ID in the "Id" field when attempting to update may cause errors.
- Network Issues: Connectivity problems to the Acumbamail API endpoint can cause timeouts or failures.
Links and References
- Acumbamail API Documentation (for detailed API usage and template structure)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)