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, allowing users to perform various operations on different CRM resources. Specifically, for the Integration Link resource with the Get operation, it retrieves details about a specific integration link by its ID. This is useful when you want to fetch metadata or configuration information about an existing integration link within your Close.com account.
Practical scenarios include:
- Automating workflows that need to verify or use integration link details.
- Synchronizing integration link data with other systems.
- Auditing or reporting on integration links programmatically.
Properties
| Name | Meaning |
|---|---|
| Link ID | The unique identifier of the integration link to retrieve. |
| Additional Fields | Optional extra parameters to customize the response: |
| Fields | Comma-separated list of specific fields to include in the response for the integration link. |
Output
The node outputs JSON data representing the integration link object retrieved from Close.com. The structure includes all standard properties of an integration link, and optionally only the specified fields if the "Fields" property is used.
No binary data output is produced by this operation.
Example output JSON snippet (simplified):
{
"id": "link_12345",
"name": "My Integration Link",
"url": "https://example.com/integration",
"status": "active",
...
}
Dependencies
- Requires an API key credential for Close.com to authenticate requests.
- The node depends on the Close.com REST API being accessible.
- No additional external dependencies beyond the Close.com API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing Link ID will cause the API call to fail.
- Insufficient permissions or invalid API credentials can result in authentication errors.
- Specifying invalid field names in the "Fields" parameter may lead to incomplete or error responses.
Error messages:
"The resource "integrationLink" is not known!"— indicates a misconfiguration or unsupported resource selection.- API errors returned from Close.com will be passed through; check the message for details like "Not Found" or "Unauthorized".
Resolutions:
- Ensure the Link ID is correct and exists in your Close.com account.
- Verify that the API key credential has appropriate permissions.
- Use valid field names as per Close.com API documentation when using the "Fields" option.