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
The node integrates with Close.com CRM to perform various operations on different resources. Specifically, for the Template resource with the Get Many operation, it retrieves multiple templates of a specified type (Email or SMS) from Close.com. This is useful when you want to fetch and process a list of communication templates stored in your CRM, for example, to automate sending emails or SMS messages using predefined templates.
Practical examples:
- Fetch all email templates to display them in a UI or use them in an automated email campaign.
- Retrieve SMS templates to send bulk SMS notifications via another service integrated into your workflow.
Properties
| Name | Meaning |
|---|---|
| Template Type | The type of template to retrieve. Options: Email (email template), SMS (SMS template) |
| Return All | Whether to return all available templates or limit the number of results |
| Limit | Maximum number of templates to return if not returning all (minimum 1, default 50) |
| Additional Fields | Optional comma-separated list of additional fields to include in the response |
Output
The output is an array of JSON objects representing the templates retrieved from Close.com. Each object contains the data fields of a template according to the requested type and any additional fields specified.
If binary data were involved (not indicated here), it would typically represent attachments or media related to templates, but this node focuses on JSON data only.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node uses Close.com's REST API endpoints to fetch template data.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Requesting too many records without setting "Return All" may result in truncated data.
- Specifying invalid template types or fields may cause API errors or empty responses.
Error messages:
"The resource "template" is not known!"— indicates an unsupported resource was selected; ensure "Template" is chosen.- API request failures usually return error messages from Close.com; verify API key validity and network connectivity.
Resolutions:
- Double-check API credentials and permissions.
- Use "Return All" carefully to avoid performance issues.
- Validate input parameters against allowed options.