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 to perform operations on various resources, including email templates. Specifically, the Email Template - Get operation retrieves details of a specified email template by its ID. This is useful when you want to fetch and use existing email templates within your workflows, for example, to preview or modify them before sending emails.
Practical scenarios include:
- Automatically retrieving an email template's content to customize it dynamically.
- Using the template data to generate emails in bulk campaigns.
- Integrating Close.com email templates into other systems or processes.
Properties
| Name | Meaning |
|---|---|
| Template ID | The unique identifier of the email template to retrieve. This is required. |
| Additional Fields | Optional collection to specify extra fields to include in the response. |
| Fields | Comma-separated list of specific fields from the email template to include in the output. |
Output
The node outputs JSON data representing the requested email template. The structure typically includes all standard properties of an email template such as its ID, name, subject, body content, and any additional fields requested via the "Fields" property.
No binary data output is indicated for this operation.
Example output JSON snippet (simplified):
{
"id": "template_123",
"name": "Welcome Email",
"subject": "Welcome to Our Service!",
"body": "<html>...</html>",
"fields": {
// any additional requested fields here
}
}
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node uses Close.com's REST API endpoints internally.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Template ID will cause the request to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Requesting non-existent fields in the "Fields" parameter may lead to incomplete or empty responses.
Error messages:
"The resource "emailTemplate" is not known!"— indicates a misconfiguration of the resource parameter.- API errors returned from Close.com (e.g., 404 Not Found if template ID does not exist).
Resolutions:
- Verify that the Template ID is correct and exists in Close.com.
- Ensure the API key credential has proper access rights.
- Use valid field names in the "Fields" parameter or leave it empty to get default fields.