Close icon

Close

Interact with Close.com CRM

Actions79

Overview

This node integrates with Close.com CRM to manage various CRM resources, including templates. Specifically, the Template - Create operation allows users to create new message templates within Close.com, supporting both email and SMS types. This is useful for automating communication workflows by reusing predefined message formats.

Typical use cases include:

  • Creating standardized email templates for marketing campaigns or customer support.
  • Defining SMS templates for quick notifications or alerts.
  • Sharing templates across a team to maintain consistent messaging.

For example, a user can create an email template with a subject, plain text body, and HTML body to send personalized emails automatically. Alternatively, they can create an SMS template with concise text content for mobile notifications.

Properties

Name Meaning
Template Type The type of template to create. Options: Email (email template), SMS (SMS template)
Name The name identifier for the template
Subject (Email only) The subject line of the email template
Body Text (Email only) Plain text version of the email body
Body HTML (Email only) HTML formatted version of the email body
Text (SMS only) The text content of the SMS template
Additional Fields > Is Shared Whether the template is shared with the team (boolean)

Output

The node outputs JSON data representing the created template object as returned by the Close.com API. This typically includes details such as the template ID, name, type, content fields, and sharing status.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to Close.com CRM via an API key credential configured in n8n.
  • The node depends on Close.com's REST API endpoints for templates.
  • No additional external services are required beyond Close.com.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Providing incomplete required fields (e.g., missing "Name" or "Subject" for email templates) will result in validation errors from the API.
    • Selecting mismatched fields for the template type (e.g., providing SMS text when creating an email template) may cause unexpected behavior or errors.

  • Error messages:

    • "The resource "template" is not known!" — indicates an invalid resource parameter; ensure "Template" is selected.
    • API error responses will be passed through; check the error message for details like missing fields or permission issues.

  • Resolution tips:

    • Verify all required fields are filled according to the template type.
    • Confirm API credentials have sufficient permissions to create templates.
    • Use the "Is Shared" option carefully, as sharing templates affects team visibility.

Links and References

Discussion