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 CRM resources such as leads, contacts, activities, opportunities, and more. Specifically, for the Lead resource with the Delete operation, the node deletes a lead identified by its unique Lead ID from the Close.com system.
This functionality is useful in scenarios where you want to automate the cleanup or management of your CRM data, such as removing outdated or invalid leads automatically based on certain triggers or workflows.
Example use case: Automatically delete leads that have been marked as duplicates or are no longer relevant after a certain period, helping maintain a clean and accurate CRM database.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to delete. This is a required string input property. |
Output
The node outputs JSON data representing the result of the delete operation for each processed item. Typically, this will include confirmation of deletion or any error messages if the deletion failed.
- The output
jsonfield contains the response from the Close.com API regarding the deleted lead. - No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Close.com via an API key credential configured in n8n.
- The node depends on the Close.com REST API to perform lead deletions.
- Proper permissions on the Close.com API key are necessary to delete leads.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: Ensure the Lead ID provided exists and is correctly formatted.
- Insufficient API permissions: The API key must have rights to delete leads.
- Network or authentication errors: Verify API credentials and network connectivity.
Error messages:
"The resource "lead" is not known!": This indicates an internal misconfiguration or unsupported resource; ensure the resource parameter is set to "lead".- API errors returned from Close.com (e.g., 404 Not Found if Lead ID does not exist): Check the Lead ID validity.
- Authentication errors: Confirm that the API key credential is valid and has not expired.