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 email templates. The "Get Many" operation for the Email Template resource allows users to retrieve multiple email templates from their Close.com account. This is useful for scenarios where you want to list, filter, or process multiple email templates in bulk, such as syncing templates to another system, auditing template usage, or dynamically selecting templates for campaigns.
Practical examples:
- Fetch all email templates to display them in a custom dashboard.
- Retrieve a limited number of templates filtered by archived status for cleanup or review.
- Get specific fields of email templates to reduce data volume and improve performance.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available email templates or limit the number of results returned. |
| Limit | Maximum number of email templates to return when "Return All" is false (minimum 1). |
| Additional Fields | Optional filters and fields: - Is Archived: Filter templates by whether they are archived. - Fields: Comma-separated list of specific fields to include in the response. |
Output
The node outputs an array of JSON objects representing email templates retrieved from Close.com. Each object corresponds to one email template and contains its properties as returned by the API. The exact fields depend on the requested fields filter if specified; otherwise, it includes default template details.
No binary data output is involved.
Example structure of one item in json output might include:
{
"id": "template_123",
"name": "Welcome Email",
"subject": "Welcome to our service!",
"body": "<html>...</html>",
"is_archived": false,
...
}
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node uses Close.com's REST API endpoints to fetch email templates.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Authentication errors due to invalid or missing API credentials.
- API rate limits being exceeded if requesting too many templates at once.
- Filtering by fields or archived status may return empty results if no templates match criteria.
Error messages:
"The resource "emailTemplate" is not known!": Indicates a misconfiguration or unsupported resource selection.- Network or API errors will typically propagate from the Close.com API; ensure network connectivity and valid credentials.
Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Use the "Limit" property to restrict the number of templates fetched to avoid timeouts or rate limits.
- Double-check filter values like "Is Archived" to ensure they match existing template statuses.