Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
The node integrates with a list management and email marketing platform, allowing users to create, modify, and manage email templates among other resources. Specifically, the "Template" resource with the "Create" operation enables users to create new email templates that can be used for campaigns or transactional emails.
This node is beneficial in scenarios where automated email marketing workflows are needed, such as setting up campaign templates dynamically or managing transactional email content programmatically. For example, a user could automate the creation of personalized campaign templates based on customer data or update transactional email templates when product information changes.
Properties
| Name | Meaning |
|---|---|
| Name | The name identifier for the template being created. |
| Subject | The subject line of the email template. |
| Type | The category of the template; options are: "Campaign" (for marketing campaigns) or "Transactional" (for system-triggered emails). |
| Body | The main content/body of the email template, supporting code editing for HTML or text. |
Output
The node outputs JSON data representing the newly created template object as returned by the API. This typically includes details such as the template ID, name, subject, type, body content, and metadata about creation. There is no indication that binary data is output by this node.
Dependencies
- Requires connection to a list management/email marketing service via its API.
- Needs an API authentication credential consisting of a domain URL, username, and password.
- The base URL for API requests is constructed from the provided domain credential.
- Requests use HTTP Basic Authentication with the supplied username and password.
- The node expects JSON responses and sends JSON payloads.
Troubleshooting
- Authentication errors: Ensure the API credentials (domain, username, password) are correct and have sufficient permissions.
- Invalid input data: Required fields like "Name" must be provided; missing or malformed inputs may cause API rejections.
- API endpoint issues: Verify the domain URL does not end with a slash to avoid malformed URLs.
- Network connectivity: Confirm network access to the API endpoint is available.
- Error messages from API: Typically include validation errors or authentication failures; review the error message details to adjust inputs or credentials accordingly.
Links and References
- Official list management/email marketing platform API documentation (refer to the specific service you connect to).
- n8n documentation on creating and using custom nodes and credentials.
- General REST API usage and HTTP Basic Authentication guides.