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 Lead resource and the Merge operation, it merges two leads by combining a source lead into a destination lead. This is useful for cleaning up duplicate lead records or consolidating information from multiple leads into one.
Practical scenarios include:
- Merging duplicate leads that were entered separately but represent the same potential customer.
- Consolidating lead data after importing leads from multiple sources.
- Maintaining clean and accurate CRM data by removing redundant entries.
Properties
| Name | Meaning |
|---|---|
| Source Lead ID | The ID of the lead to merge (source). This lead's data will be merged into the destination lead. |
| Destination Lead ID | The ID of the lead to merge into (destination). This lead will retain the combined data after the merge. |
Output
The node outputs JSON data representing the result of the merge operation. This typically includes details about the merged lead record, such as its updated fields and status. If the operation fails for any input item, an error message is returned in the output JSON under an error field.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Close.com CRM API.
- The node depends on the Close.com HTTP API endpoints to perform lead merging and other CRM operations.
- Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing lead IDs: Ensure both source and destination lead IDs are correct and exist in Close.com.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and Close.com service status.
Error messages:
"The resource "lead" is not known!": This indicates an unsupported resource was selected; ensure "Lead" is chosen.- Errors returned from the API will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled.
To resolve errors, verify input parameters, credentials, and network connectivity.