Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically enabling interaction with its CRM and telephony features. The "Search CRM Entities" operation under the "Telephony" resource allows users to search for CRM records based on a phone number. This is useful in scenarios such as identifying the caller's contact or lead information during an incoming call or logging call details linked to CRM entities.

Practical examples include:

  • Automatically retrieving customer details when a call is received by searching CRM contacts or leads by the caller's phone number.
  • Enriching call logs with CRM entity data for better tracking and follow-up.
  • Triggering workflows based on the CRM entity found via the phone number.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key.
Phone Number The phone number used to search CRM entities related to that number.

Output

The node outputs JSON data representing the CRM entities found matching the provided phone number. The structure typically includes details about the matched CRM records such as contacts, leads, or other relevant entities associated with the phone number.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs an object containing:

  • error: The error message.
  • resource: The resource name ("telephony").
  • timestamp: The ISO timestamp of the error occurrence.

No binary data output is indicated for this operation.

Dependencies

  • Requires authentication credentials for Bitrix24, which can be configured using OAuth2, a webhook URL, or an API key.
  • Relies on Bitrix24 API endpoints to perform CRM searches and retrieve entity data.
  • The node uses internal helper functions to make standardized API calls to Bitrix24.

Troubleshooting

  • Common Issues:

    • Incorrect or expired authentication credentials may cause authorization failures.
    • Providing an invalid or improperly formatted phone number could result in no matches or errors.
    • Network connectivity issues might prevent successful API calls.
  • Error Messages:

    • Errors returned from Bitrix24 API calls will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures, rate limits, or invalid parameters.
  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the phone number is correctly formatted according to Bitrix24 requirements.
    • Check network connectivity and Bitrix24 service status.

Links and References

Discussion