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
This node integrates with the Bitrix24 CRM and business platform, specifically providing functionality to find duplicate entities within the CRM. The "Find Duplicates" operation under the "Duplicate" resource allows users to search for duplicate records of a specified entity type (such as Lead, Deal, Contact, or Company) based on different matching criteria.
Common scenarios where this node is beneficial include:
- Cleaning up CRM data by identifying duplicate leads or contacts.
- Automating workflows that require merging or handling duplicates.
- Maintaining data integrity in sales and marketing pipelines.
For example, a user can input an entity ID of a lead and use this node to find other leads that are exact or similar duplicates, helping to avoid redundant outreach or conflicting data entries.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Entity Type | Type of entity to search for duplicates. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the entity to find duplicates for. |
| Options | Additional options for searching duplicates: |
| - Match Type | Type of duplicate matching: Exact, Similar, or Fuzzy. |
| - Access Token | Optional access token for authentication (used if needed). |
Output
The node outputs JSON data containing the results of the duplicate search. The structure typically includes details about the found duplicate entities related to the specified entity ID and entity type. Each output item represents a duplicate record with its associated fields as returned by the Bitrix24 API.
If the node encounters an error during execution, it outputs a JSON object with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 CRM via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch duplicate information.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
- Authentication Errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 is recommended for production environments.
- Invalid Entity ID: Providing a non-existent or incorrect entity ID will result in no duplicates found or errors. Verify the entity ID before running the node.
- API Rate Limits or Connectivity Issues: Network problems or Bitrix24 API rate limits may cause failures. Check network connectivity and API usage quotas.
- Error Messages: If the node throws an error, it will be included in the output JSON under the
errorkey. Review the message for clues, such as permission issues or invalid parameters. - Continue On Fail: If enabled, the node will output error information instead of stopping workflow execution, allowing for graceful error handling.