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 such as leads, contacts, activities, opportunities, and more. Specifically, for the Contact resource with the Delete operation, the node deletes a contact from the Close.com CRM by its unique Contact ID.
This functionality is useful in scenarios where you want to automate the cleanup or management of your CRM contacts, for example:
- Automatically removing contacts that have unsubscribed or are no longer relevant.
- Syncing deletions from another system into Close.com.
- Bulk deleting contacts based on certain criteria via workflows.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation for each input item. Typically, this will include confirmation of deletion or any error messages if the deletion failed.
If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the resource, but for the Delete operation on Contact, only JSON output is expected.
Dependencies
- Requires an API key credential for Close.com CRM to authenticate requests.
- The node depends on the Close.com REST API endpoints to perform actions.
- No additional external services are required beyond the Close.com API.
- Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Contact ID will cause the operation to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity issues preventing access to Close.com API.
- Attempting to delete a contact that does not exist will likely return an error.
Error messages:
"The resource "contact" is not known!"— indicates an invalid resource parameter; ensure "Contact" is selected.- API errors returned from Close.com will be passed through; check the message for details like "Contact not found" or "Unauthorized".
Resolutions:
- Verify the Contact ID is correct and exists in Close.com.
- Check and update the API key credential.
- Ensure network connectivity and API endpoint accessibility.
- Use the "Continue On Fail" option in the node settings to handle errors gracefully in bulk operations.