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 interacts with Close.com CRM to perform various operations on different resources. Specifically, for the Email Template resource with the Render operation, it renders an email template either for a specific lead and contact or based on results from a search query.
Common scenarios include:
- Generating personalized email content for a particular lead-contact pair before sending.
- Rendering email templates dynamically for leads or contacts retrieved via a search query, useful in bulk or automated email campaigns.
Practical examples:
- Render an email template for Lead ID
123and Contact ID456to preview or send a customized message. - Use a search query like
{ "status": "potential" }to render the template for the first lead or contact matching that status.
Properties
| Name | Meaning |
|---|---|
| Template ID | The unique identifier of the email template to render. |
| Render Mode | How to render the email template: - Single Lead/Contact: Render for a specific lead and contact. - Search Query: Render for results from a search query. |
| Lead ID | (Required if Render Mode is Single Lead/Contact) The ID of the lead to render the template for. |
| Contact ID | (Required if Render Mode is Single Lead/Contact) The ID of the contact to render the template for. |
| Query | (Required if Render Mode is Search Query) The JSON-formatted search query to find leads or contacts for rendering (e.g., {"status": "potential"}). |
| Additional Fields | (Optional, only for Search Query mode) Extra options: - Entry: Index (0-99) of the lead/contact to render. - Mode: Whether to render for the lead's first contact or the contact itself at the given entry index. |
Output
The node outputs JSON data representing the rendered email template content. This typically includes the fully processed email body with all placeholders replaced according to the specified lead/contact or search query context.
If binary data output were supported (not indicated here), it would represent attachments or other non-JSON content related to the rendered email.
Dependencies
- Requires an API key credential for authenticating with Close.com CRM.
- The node depends on Close.com's API endpoints for email templates and lead/contact data.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Template ID: If the provided template ID does not exist or is incorrect, the node will likely throw an error indicating the template was not found. Verify the template ID is correct.
- Missing Lead or Contact IDs: When using Single Lead/Contact render mode, both Lead ID and Contact ID must be provided. Omitting these will cause errors.
- Malformed Search Query: The query property must be valid JSON. Invalid JSON syntax will cause parsing errors.
- Entry Index Out of Range: For Search Query mode, the entry index should be between 0 and 99. Values outside this range may cause errors or unexpected behavior.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access email templates and lead/contact data.
- Network Issues: Connectivity problems with Close.com API endpoints can cause timeouts or failures.