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 perform various operations on Bitrix24 resources. Specifically, for the Duplicate resource with the Disable Duplicate Control operation, it disables the duplicate control feature in Bitrix24, which is used to prevent or manage duplicate records within the CRM.
Common scenarios where this node is beneficial include:
- Automating CRM data management workflows where duplicate detection needs to be temporarily disabled.
- Integrating Bitrix24 with other systems that may require bypassing duplicate checks during bulk imports or updates.
- Managing CRM settings programmatically as part of larger automation pipelines.
Example use case:
- A user wants to import a large list of contacts into Bitrix24 without triggering duplicate warnings. They can use this node to disable duplicate control before the import and re-enable it afterward.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
The node also requires selecting the Resource and Operation, but since the focus is on the "Duplicate" resource and "Disable Duplicate Control" operation, these are implicitly set.
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after processing the requested operation.
- The
jsonoutput typically contains the result of disabling duplicate control, such as success confirmation or error details. - If an error occurs and the node is configured to continue on failure, the output includes an
errorfield with the error message, theresourcename, and a timestamp. - No binary data output is indicated in the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use)
- Webhook URL authentication (simpler but less secure)
- API Key authentication
- The node depends on internal helper modules for making API calls to Bitrix24 and handling resources.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API call errors if the Bitrix24 instance is unreachable or the user lacks permissions.
- Misconfiguration of the resource or operation parameters.
Error messages:
- Errors thrown by the Bitrix24 API will be caught and returned in the output if "Continue On Fail" is enabled.
- Typical error messages might include authorization errors, invalid parameters, or network timeouts.
Resolution tips:
- Verify that the correct authentication method and valid credentials are used.
- Ensure the Bitrix24 account has sufficient permissions to modify duplicate control settings.
- Check network connectivity and API endpoint availability.
- Use the "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Bitrix24 Official Documentation
- Bitrix24 API Reference
- n8n documentation on creating custom nodes