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 a CRM system to perform various operations on different resources, including email templates. Specifically, the Email Template - Update operation allows users to modify existing email templates by changing properties such as the template's name, subject line, HTML body, plain text body, and flags indicating whether the template is shared or archived.
This operation is useful in scenarios where you want to programmatically update email templates stored in your CRM without manually editing them through the CRM interface. For example, you might automate updating seasonal promotional email templates or adjust templates based on campaign performance data.
Properties
| Name | Meaning |
|---|---|
| Template ID | The unique identifier of the email template to update. |
| Update Fields | A collection of fields to update on the email template. Options include: |
| Name | The new name for the email template. |
| Subject | The new subject line for the email template. |
| Body HTML | The new HTML content for the email template's body. |
| Body Text | The new plain text content for the email template's body. |
| Is Shared | Boolean flag indicating if the template should be shared with the organization. |
| Is Archived | Boolean flag indicating if the template should be marked as archived. |
Output
The node outputs an array of JSON objects representing the results of the update operation(s). Each output item corresponds to one input item processed and contains the updated email template data returned from the CRM API.
If the node encounters errors during execution and "Continue On Fail" is enabled, the output will include JSON objects with an error field describing the issue for that particular item.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the CRM service.
- The node depends on the CRM's REST API endpoints for email template management.
- Proper network connectivity to the CRM API endpoint is necessary.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing Template ID: The update will fail if the specified template ID does not exist.
- Insufficient permissions: The API key used must have rights to update email templates.
- Network or API errors: Connectivity issues or API rate limits may cause failures.
Error Messages:
"The resource "emailTemplate" is not known!": This indicates an invalid resource parameter; ensure "Email Template" is selected.- Errors returned from the CRM API (e.g., 404 Not Found, 401 Unauthorized) will be surfaced in the node output if "Continue On Fail" is enabled.
Resolution Tips:
- Verify the Template ID is correct and exists in the CRM.
- Check API credentials and permissions.
- Enable "Continue On Fail" to handle partial failures gracefully.
- Review API limits and retry policies if rate limiting occurs.
Links and References
- Close.com API Documentation - Email Templates (example link, replace with actual CRM API docs)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.