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 operation allows users to create a "Smart View" in the Close.com CRM system. A Smart View is essentially a saved search or filtered view that helps users quickly access leads or contacts matching specific criteria. By defining a query in JSON format, users can customize which records appear in the Smart View based on various fields and conditions.
Common scenarios where this node is beneficial include:
- Automatically creating filtered lists of leads or contacts for targeted marketing campaigns.
- Organizing CRM data by dynamically grouping records with shared attributes (e.g., status, custom fields).
- Sharing specific views with team members to streamline collaboration and focus on relevant subsets of data.
Practical example:
- Create a Smart View named "Hot Leads" that filters leads with status "potential" and a custom field indicating high interest.
- Create a shared Smart View for contacts located in a particular region to coordinate regional sales efforts.
Properties
| Name | Meaning |
|---|---|
| Name | The name assigned to the Smart View being created. |
| Query | The search query expressed in JSON format that defines the filter criteria for the Smart View. |
| Smart View Type | The type of Smart View to create; options are: Lead Smart View or Contact Smart View. |
| Additional Fields | Optional additional settings; currently supports: |
| - Shared | Boolean flag indicating whether the Smart View should be shared with the entire organization (true/false). |
Output
The node outputs an array of JSON objects representing the created Smart View(s). Each output item contains details about the newly created Smart View, including its identifier, name, type, query, and sharing status.
If the node supports binary data output, it is not indicated here; the output focuses on JSON data describing the Smart View.
Dependencies
- Requires an active connection to the Close.com CRM API using a valid API authentication token.
- The node depends on proper configuration of credentials within n8n to authenticate requests to Close.com.
- No other external services or environment variables are explicitly required.
Troubleshooting
Common issues:
- Invalid JSON format in the "Query" property may cause request failures. Ensure the JSON is well-formed and matches expected query structure.
- Insufficient permissions or invalid API credentials will result in authentication errors.
- Attempting to create a Smart View with a duplicate name might cause conflicts depending on Close.com's API behavior.
Error messages:
"The resource "smartView" is not known!"— This indicates the resource parameter was incorrectly set or missing.- API errors returned from Close.com will typically include HTTP status codes and error messages; verify credentials and query correctness.
Resolution tips:
- Validate JSON queries using online JSON validators before input.
- Confirm API credentials are correctly configured and have necessary scopes.
- Use the "Shared" option carefully, as sharing views affects organizational visibility.