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 to retrieve multiple "Smart Views," which are saved searches or filtered views within Close.com. The "Get Many" operation under the "Smart View" resource allows users to fetch a list of these smart views, optionally filtered by type and other criteria.
Typical use cases include:
- Automating workflows that need to process or analyze multiple saved searches from Close.com.
- Synchronizing smart view data with other systems or databases.
- Dynamically retrieving smart views for reporting or dashboarding purposes.
For example, a user might want to get all smart views related to leads or contacts to trigger further processing or notifications based on those views.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available smart views or limit the number of results returned. |
| Limit | Maximum number of smart views to return if "Return All" is false. Minimum value is 1. |
| Filter Options | Additional filters to narrow down the smart views retrieved: |
| - Type | Filter smart views by type. Options: "Lead" or "Contact". |
| - Type In | Comma-separated list of types to include (e.g., "lead,contact"). |
| - Fields | Comma-separated list of specific fields to include in the response for each smart view. |
Output
The node outputs an array of JSON objects representing the smart views retrieved from Close.com. Each object corresponds to one smart view and contains its properties as returned by the API, potentially filtered by the requested fields.
If binary data were involved (not indicated here), it would be summarized accordingly, but this node deals only with JSON data.
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node uses Close.com's REST API endpoints to fetch smart views.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common Issues:
- Authentication errors due to invalid or missing API credentials.
- Exceeding API rate limits imposed by Close.com.
- Providing invalid filter values (e.g., unsupported types) may result in empty responses or errors.
- Network connectivity issues affecting API calls.
Error Messages:
"The resource "smartView" is not known!"— This indicates an internal misconfiguration or typo in the resource parameter.- API error messages from Close.com will be passed through; check the message for details such as authentication failure or invalid parameters.
Resolutions:
- Verify that the API key credential is correctly configured and has sufficient permissions.
- Ensure filter options are valid and formatted correctly.
- Use the "Return All" option carefully to avoid large data loads that could time out.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.
Links and References
- Close.com API Documentation
- n8n Documentation on Credentials
- Close.com Smart Views Overview (for conceptual understanding)