Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

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 json output 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 error field with the error message, the resource name, 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

Discussion