Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with the Close.com CRM platform, allowing users to perform various operations on different CRM resources. Specifically, for the Email Template - Create operation, it enables creating new email templates within Close.com. This is useful for automating the management of email templates used in sales or marketing campaigns, ensuring consistent messaging and saving time by reusing predefined templates.
Practical examples include:
- Automatically creating standardized email templates when onboarding new products or services.
- Managing shared email templates across an organization to maintain brand consistency.
- Archiving outdated templates programmatically to keep the template list clean.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the email template to be created. |
| Subject | The subject line that will appear in emails sent using this template. |
| Body HTML | The HTML content of the email body, supporting rich formatting and styling. |
| Additional Fields | Optional extra settings for the template: |
| - Body Text | Plain text version of the email body for clients that do not support HTML. |
| - Is Shared | Boolean flag indicating if the template should be shared with the entire organization. |
| - Is Archived | Boolean flag indicating if the template is archived (not actively used). |
Output
The node outputs JSON data representing the newly created email template as returned by the Close.com API. This typically includes details such as the template's unique identifier, name, subject, HTML body, plain text body (if provided), sharing status, and archival status.
No binary data output is involved in this operation.
Dependencies
- Requires a valid API key credential for Close.com configured in n8n to authenticate requests.
- Relies on Close.com's REST API endpoints for managing email templates.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Missing required fields (
Name,Subject, orBody HTML) will cause the API to reject the creation request. - Invalid API credentials or insufficient permissions can result in authentication errors.
- Network connectivity problems may prevent communication with Close.com's API.
- Missing required fields (
Error messages:
"The resource "emailTemplate" is not known!"— indicates a misconfiguration of the resource parameter; ensure "Email Template" is selected.- API error responses typically include descriptive messages; check the node's output for detailed error info.
Resolutions:
- Verify all required input properties are correctly set.
- Confirm the API key credential is valid and has appropriate permissions.
- Check network access and proxy settings if applicable.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.