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 interacts with the Close.com CRM platform, specifically focusing on the "Integration Link" resource with the "Get Many" operation. It retrieves multiple integration links from Close.com, allowing users to fetch either all available links or a limited subset based on specified criteria. This is useful for workflows that need to synchronize or analyze integration link data, such as reporting on linked entities or automating processes based on integration link attributes.
Practical examples include:
- Fetching all integration links of type "lead" to process lead-related integrations.
- Retrieving a limited number of integration links filtered by type to optimize performance and focus on relevant data subsets.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit (true/false). |
| Limit | Maximum number of results to return when "Return All" is false. Minimum value is 1. |
| Filter Options | Additional filters to narrow down results: |
| - Type | Filter links by type; options are "Lead", "Contact", or "Opportunity". |
| - Fields | Comma-separated list of fields to include in the response, allowing partial data retrieval. |
Output
The node outputs an array of JSON objects representing integration links retrieved from Close.com. Each object contains the properties of an integration link according to the requested fields or default fields if none specified.
If binary data were involved, it would be summarized here, but this node deals solely with JSON data representing integration links.
Dependencies
- Requires an API key credential for authenticating with Close.com CRM.
- The node depends on the Close.com API being accessible and properly configured.
- No additional external services are required beyond Close.com's API.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or missing API credentials.
- API rate limits or network connectivity issues causing request failures.
- Incorrect filter values leading to empty result sets.
Error Messages:
"The resource \"integrationLink\" is not known!"— indicates an unsupported resource was selected; ensure "Integration Link" is chosen.- Errors related to API requests typically include messages about authentication or request limits; verify API key validity and usage quotas.
Resolutions:
- Confirm the API key credential is correctly set up in n8n.
- Check network connectivity and Close.com service status.
- Adjust filters and limits to valid values.
Links and References
- Close.com API Documentation
- n8n Documentation on Credentials
- Close.com Integration Node in n8n Community
Note: This summary is based on static analysis of the node's source code and provided property definitions without runtime execution.