Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 CRM and business platform, enabling users to interact programmatically with various Bitrix24 resources. Specifically, for the "Data Storage" resource and the "Get Entity Sections" operation, it retrieves structured sections or segments of a specified entity within Bitrix24. This is useful for workflows that need to dynamically access metadata or segmented data related to CRM entities such as contacts, deals, leads, companies, etc.

Common scenarios include:

  • Automating data retrieval for reporting or synchronization with other systems.
  • Dynamically fetching entity sections to customize UI forms or data processing logic.
  • Integrating Bitrix24 entity data into broader automation pipelines.

Example: A user might configure this node to get all sections of a "Deal" entity to understand its structure before updating or analyzing deal data in an external system.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key

The node also requires selecting the Resource ("Data Storage" in this context) and the Operation ("Get Entity Sections"), but these are fixed by your input.

Output

The node outputs an array of JSON objects representing the sections of the requested Bitrix24 entity. Each item in the output corresponds to a section with its associated fields and metadata as returned by the Bitrix24 API.

If an error occurs during execution, and the node is configured to continue on failure, 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 valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2 token, webhook URL, or API key.
  • Uses internal helper functions to make standardized API calls to Bitrix24 endpoints.
  • No additional external services beyond Bitrix24 itself.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or expired credentials.
    • API rate limits or permission restrictions from Bitrix24.
    • Network connectivity problems affecting API calls.
  • Error messages:

    • Errors thrown during API calls will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Messages typically include the API error message and the resource involved.
  • Resolutions:

    • Verify and refresh authentication credentials.
    • Check Bitrix24 API permissions and scopes.
    • Ensure network access to Bitrix24 endpoints.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References


Note: The summary focuses on the "Data Storage" resource and "Get Entity Sections" operation as requested, based on static analysis of the provided source code and property definitions.

Discussion