Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
The node integrates with the Bitrix24 CRM and business platform, specifically providing functionality to merge duplicate entities within the CRM. The "Merge Duplicates" operation under the "Duplicate" resource allows users to consolidate duplicate records of a specified entity type (such as Leads, Deals, Contacts, or Companies) by merging them into a single record.
This is beneficial in scenarios where data cleanliness and deduplication are critical, such as maintaining accurate customer databases, avoiding redundant communications, and ensuring consistent reporting. For example, if multiple contact entries exist for the same person, this node can merge those duplicates into one unified contact record.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler, less secure), or API Key authentication. |
| Entity Type | The type of CRM entity to search for duplicates and merge. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the specific entity instance to be merged with its duplicates. |
Output
The node outputs JSON data representing the result of the merge operation. This typically includes details about the merged entity, confirmation of success, or error information if the merge failed.
If an error occurs during execution and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to a Bitrix24 account via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints to perform duplicate detection and merging.
- Proper API credentials or tokens must be configured in n8n for authentication.
- Network access to Bitrix24 services is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials may cause authorization failures.
- Providing an incorrect or non-existent Entity ID will result in errors or no action.
- Insufficient permissions in Bitrix24 to perform merge operations can cause failures.
- Network connectivity issues may prevent API calls from succeeding.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled. - Typical messages might include authentication errors, invalid parameters, or permission denials.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolution Tips:
- Verify that the authentication method and credentials are correctly set up and valid.
- Confirm the Entity ID exists and corresponds to the selected Entity Type.
- Ensure the Bitrix24 user has adequate permissions to merge duplicates.
- Check network connectivity and firewall settings.