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 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.