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 enabling operations on various CRM resources. For the Smart View resource with the Get operation, it retrieves details of a saved search (smart view) by its ID. This is useful when you want to programmatically access predefined filtered views of your CRM data, such as leads or opportunities, without manually navigating the Close.com interface.
Practical examples include:
- Automatically fetching a smart view to process or analyze the filtered data it represents.
- Using the smart view's configuration to dynamically adjust workflows based on saved search criteria.
- Integrating smart view data into reports or dashboards outside Close.com.
Properties
| Name | Meaning |
|---|---|
| Smart View ID | The unique identifier of the smart view to retrieve. |
| Additional Fields | Optional extra parameters; currently supports: - Fields: Comma-separated list of specific fields to include in the response. |
Output
The node outputs JSON data representing the retrieved smart view object from Close.com. This includes all standard properties of the smart view unless limited by the "Fields" parameter. The output structure corresponds to the smart view's attributes as defined by Close.com's API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Close.com via an API key credential configured in n8n.
- The node depends on Close.com's REST API endpoints for smart views.
- Proper permissions on the Close.com account are necessary to read smart view data.
Troubleshooting
Common issues:
- Invalid or missing Smart View ID will cause the request to fail.
- Insufficient API permissions may result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
"The resource "smartView" is not known!"— This indicates an internal error in resource selection; ensure the resource parameter is correctly set to "smartView".- API errors returned from Close.com (e.g., 404 Not Found if the smart view ID does not exist) should be checked by verifying the ID and user permissions.
- If the node throws an error about missing credentials, verify that the API key credential is properly configured in n8n.