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, allowing users to interact with various Bitrix24 resources programmatically. Specifically, for the Duplicate resource and the Get Duplicate Criteria operation, it retrieves criteria used by Bitrix24 to identify duplicate records within the CRM.
Common scenarios where this node is beneficial include:
- Automating data quality checks by fetching duplicate detection rules.
- Integrating Bitrix24 duplicate criteria into workflows that clean or merge duplicate CRM entries.
- Synchronizing duplicate detection settings across multiple Bitrix24 accounts or environments.
For example, a user might use this node to fetch the current duplicate criteria for contacts and then apply custom logic to handle duplicates in an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of JSON objects representing the result of the requested operation. For the Get Duplicate Criteria operation under the Duplicate resource, the output JSON contains the duplicate detection criteria as defined in Bitrix24.
If an error occurs and "Continue On Fail" is enabled, the output will contain an object with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24's REST API endpoints internally to fetch data.
- The node depends on internal helper modules for making API calls and handling resources, but no external npm packages are explicitly required beyond those bundled.
Troubleshooting
Common issues:
- Incorrect or expired authentication credentials can cause API call failures.
- Network connectivity problems may prevent communication with Bitrix24 servers.
- If the specified resource or operation is invalid or unsupported, the node will throw an error.
Error messages:
- Errors from Bitrix24 API calls are propagated and included in the output if "Continue On Fail" is enabled.
- Typical errors include authentication failures, permission denied, or invalid parameters.
Resolution tips:
- Verify that the selected authentication method is correctly configured with valid credentials.
- Ensure the Bitrix24 account has sufficient permissions to access duplicate criteria.
- Check network connectivity and firewall settings.
- Enable "Continue On Fail" to capture error details in the workflow for debugging.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 CRM Duplicate Management
- n8n documentation on creating custom nodes