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 and the Delete operation, the node deletes an existing integration link identified by its ID.
Common scenarios where this node is beneficial include automating the management of integration links within Close.com, such as cleaning up obsolete or invalid integration connections programmatically without manual intervention.
For example, if you have multiple integration links set up for syncing data between Close.com and other services, and some are no longer needed, you can use this node to delete those links automatically based on your workflow logic.
Properties
| Name | Meaning |
|---|---|
| Link ID | The unique identifier of the integration link to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the integration link was successfully deleted or provide error information if the deletion failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Close.com API.
- The node depends on the Close.com REST API endpoint for managing integration links.
- Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Link ID will cause the delete operation to fail.
- Missing or incorrect API authentication credentials will prevent the node from connecting to Close.com.
- Network connectivity issues may cause request timeouts or failures.
Error messages:
"The resource "integrationLink" is not known!"— indicates that the resource parameter is incorrect or unsupported.- API errors returned from Close.com (e.g., 404 Not Found if the Link ID does not exist) will be surfaced in the node's output.
Resolutions:
- Verify the Link ID is correct and exists in your Close.com account.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- Close.com API Documentation
- Close.com Integration Links API Reference (for details on integration link management endpoints)