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 Close.com CRM to perform various operations on different resources. Specifically, for the Smart View - Update operation, it allows users to update an existing saved search (smart view) in Close.com. Smart Views are customizable filters or queries that help organize and segment leads or contacts based on specific criteria.
Typical use cases include:
- Renaming a smart view to better reflect its purpose.
- Modifying the search query to refine which records appear in the smart view.
- Changing the sharing settings to control visibility within the organization.
- Switching the type of smart view between leads and contacts.
For example, a sales team might update a smart view to focus on leads with a new status or custom field value, or share a smart view with the entire organization to align team efforts.
Properties
| Name | Meaning |
|---|---|
| Smart View ID | The unique identifier of the smart view to update. |
| Update Fields | A collection of fields to update on the smart view: |
| Name | The new name for the smart view. |
| Query | The new search query in JSON format, e.g., {"status": "potential", "custom_field": "value"}. |
| Shared | Boolean indicating if the smart view should be shared with the entire organization. |
| Type | The type of the smart view, either "lead" or "contact". |
Output
The node outputs JSON data representing the updated smart view object as returned by the Close.com API. This typically includes the updated properties such as the smart view's ID, name, query, sharing status, and type.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to Close.com CRM via an API key credential configured in n8n.
- The node depends on the Close.com API endpoints for smart views.
- Proper permissions on the Close.com account to update smart views are necessary.
Troubleshooting
Common Issues:
- Invalid or missing Smart View ID will cause the update to fail.
- Malformed JSON in the Query field can result in API errors.
- Insufficient permissions to update smart views may lead to authorization errors.
- Network or API downtime can cause request failures.
Error Messages:
"The resource "smartView" is not known!"— indicates an invalid resource parameter; ensure "Smart View" is selected.- API error messages related to invalid input or authentication will be passed through; check credentials and input formatting.
Resolutions:
- Verify the Smart View ID exists and is correct.
- Validate JSON syntax in the Query field before running.
- Confirm API credentials have appropriate scopes.
- Enable "Continue On Fail" in the node settings to handle partial failures gracefully.