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 interacts with the Bitrix24 CRM and business platform, specifically providing functionality to find duplicate records based on communication details such as phone numbers or email addresses. The "Find By Communication" operation under the "Duplicate" resource allows users to search for duplicates by specifying a communication type (phone or email) and the corresponding value.
Common scenarios where this node is beneficial include:
- Identifying duplicate contacts or leads in Bitrix24 by their phone number or email address.
- Cleaning up CRM data by detecting repeated entries before importing new data.
- Automating workflows that require validation of unique communication channels.
For example, a user can input an email address to find all duplicate CRM entities associated with that email, helping maintain data integrity.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Communication Type | Type of communication to search by; options are Phone or Email. |
| Communication Value | The actual phone number or email address to search for duplicates. |
| Options | Additional optional parameters: |
| - Entity ID | Specific entity ID to exclude from the duplicate search (useful to avoid self-matching). |
| - Access Token | Access token string for authentication (alternative to main credentials). |
Output
The node outputs JSON data representing the results of the duplicate search. This typically includes information about the found duplicate entities matching the specified communication criteria.
If an error occurs during execution and the node is configured to continue on failure, the output will contain an error object with fields:
error: The error message.resource: The resource name ("duplicate").timestamp: The ISO timestamp when the error occurred.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication with Bitrix24 via one of the supported methods: OAuth2, Webhook URL, or API Key.
- The node depends on Bitrix24's API endpoints to perform the duplicate search.
- Proper configuration of credentials within n8n is necessary to authenticate API calls.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens may cause authorization failures.
- Incorrect communication type or malformed communication value can lead to no results or errors.
- Excluding an entity ID that does not exist or is incorrect might affect search accuracy.
Error Messages:
- Errors returned from Bitrix24 API calls will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical errors include authentication failures, invalid parameters, or network issues.
Resolutions:
- Verify that the selected authentication method is correctly configured and active.
- Ensure the communication value matches the expected format for phone numbers or emails.
- Check network connectivity and Bitrix24 service status if API calls fail.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 CRM Duplicate Management
- n8n Documentation on Creating Custom Nodes