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 Close.com CRM to perform operations on various resources, including templates. Specifically, for the Template resource and the Get operation, it retrieves details of a specified template by its ID. The template can be either an email or SMS template.
Common scenarios where this node is beneficial include:
- Fetching the content and metadata of a specific email or SMS template stored in Close.com for use in automated messaging workflows.
- Retrieving template details to dynamically customize messages before sending them out.
- Integrating template data into other systems or processes that require access to predefined message formats.
Practical example:
- A marketing automation workflow fetches an email template by its ID, modifies some placeholders, and sends personalized emails to leads.
Properties
| Name | Meaning |
|---|---|
| Template Type | The type of template to retrieve. Options: Email (email template), SMS (SMS template) |
| Template ID | The unique identifier of the template to get |
| Additional Fields | Optional comma-separated list of additional fields to include in the response |
Output
The node outputs JSON data representing the requested template's details. This typically includes the template's content, metadata, and any additional fields requested.
If binary data were involved (e.g., attachments), it would be included in the binary output field, but for templates, the output is primarily JSON.
Example output structure (simplified):
{
"id": "template_id",
"type": "email",
"name": "Welcome Email",
"subject": "Welcome to our service!",
"body": "<html>...</html>",
"fields": {
// additional requested fields here
}
}
Dependencies
- Requires an API key credential for Close.com CRM configured in n8n.
- The node uses Close.com's REST API endpoints to fetch template data.
- No other external dependencies are required.
Troubleshooting
Error: The resource "template" is not known!
This indicates an invalid resource parameter; ensure "Template" is selected as the resource.Error: Missing or invalid Template ID
Make sure the Template ID property is provided and correctly references an existing template in Close.com.API authentication errors
Verify that the API key credential is valid and has sufficient permissions to access templates.Empty or incomplete response
If using the "Additional Fields" option, ensure the field names are correct and available for the template resource.