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, specifically providing operations on various CRM resources including templates. The "Template" resource allows users to manage email and SMS templates used in their communications.
The Update operation for the Template resource enables modifying existing email or SMS templates by specifying the template type (Email or SMS), the template ID, and the fields to update such as name, subject, body content, and sharing status.
Common scenarios:
- Updating an email template's subject or HTML body after a campaign change.
- Modifying SMS template text content to reflect new promotions.
- Changing whether a template is shared across the team.
Practical example:
A marketing automation workflow could use this node to dynamically update an email template's subject and body before sending out a batch of emails, ensuring the content is always current without manual edits in Close.com.
Properties
| Name | Meaning |
|---|---|
| Template Type | Choose between "Email" or "SMS" template types to specify which kind of template to update. |
| Template ID | The unique identifier of the template to update. |
| Update Fields | Collection of fields to update on the template: |
| - Name | The new name for the template. |
| - Subject (Email) | The subject line for an email template. |
| - Body Text (Email) | Plain text version of the email body. |
| - Body HTML (Email) | HTML content for the email body. |
| - Text (SMS) | Text content for the SMS template. |
| - Is Shared | Boolean flag indicating if the template should be shared with the team. |
Output
The node outputs JSON data representing the updated template object returned from Close.com after the update operation. This typically includes the template's ID, updated fields, and metadata confirming the changes.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with Close.com.
- The node depends on Close.com's REST API endpoints for templates.
- Proper network connectivity to Close.com's API is necessary.
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common issues:
- Invalid or missing Template ID will cause the update to fail.
- Providing fields incompatible with the selected template type (e.g., setting email subject on an SMS template) may result in errors or ignored fields.
- Network or authentication failures due to invalid API keys.
Error messages:
"The resource "template" is not known!"— indicates an incorrect resource parameter; ensure "template" is selected.- API errors from Close.com will be passed through, often indicating invalid IDs or permission issues.
Resolutions:
- Verify the Template ID exists and belongs to the authenticated user/account.
- Match the update fields correctly to the template type.
- Confirm API credentials are valid and have sufficient permissions.
Links and References
- Close.com API Documentation - Templates
- Close.com Official Website
- n8n Documentation on Creating Custom Nodes