Actions83
- Lead Actions
- Lead Status Actions
- Contact Actions
- Opportunity Actions
- Opportunity Status Actions
- Task Actions
- Note Actions
- Call Actions
- Email Actions
- Meeting Actions
- SMS Actions
- Custom Activity Actions
- Sequence (Automation & Bulk Actions) Actions
- Bulk Action (Automation & Bulk Actions) Actions
- Export (Automation & Bulk Actions) Actions
- Field Enrichment (Automation & Bulk Actions) Actions
Lead → Merge
AI-generatedOverview
This node operation merges two leads in the Close CRM system. It takes a source lead ID and a destination lead ID as inputs, merges the source lead into the destination lead, and deletes the source lead. This operation is useful for consolidating duplicate leads or combining lead information to maintain a clean and organized CRM database.
Use Case Examples
- Merging duplicate leads where one lead's data needs to be preserved and the other removed.
- Combining leads from different sources into a single lead record for unified tracking.
Properties
| Name | Meaning |
|---|---|
| Source Lead ID | The ID of the lead to merge from (this lead will be deleted) |
| Destination Lead ID | The ID of the lead to merge into (this lead will remain) |
Output
JSON
id- The ID of the merged lead or confirmation of the merge operationsource- The source lead ID that was merged and deleteddestination- The destination lead ID that remains after the merge
Dependencies
- Close CRM API access with appropriate credentials
Troubleshooting
- Ensure both Source Lead ID and Destination Lead ID are provided; missing either will cause an error.
- Verify that the lead IDs exist in the Close CRM system before attempting to merge.
- Handle API errors gracefully, such as permission issues or network problems, by checking error messages and retrying if necessary.