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, enabling users to interact with various Bitrix24 resources and operations. Specifically, for the Telephony resource and the Get Voximplant SIP Connector operation, it allows retrieving information about a Voximplant SIP connector configured in Bitrix24 telephony settings.
Common scenarios where this node is beneficial include:
- Automating telephony system configurations by fetching SIP connector details.
- Integrating Bitrix24 telephony data into workflows for call routing or logging.
- Synchronizing telephony connectors with external systems or monitoring their status.
For example, a user might use this node to programmatically retrieve SIP connector details before initiating calls or updating telephony settings based on connector status.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of items, each containing a json object with the data returned from Bitrix24 for the requested resource and operation.
- The
jsonfield contains the response data from Bitrix24's API related to the Voximplant SIP connector. - If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an
errormessage, theresourcename, and atimestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses internal helper functions to make standardized API calls to Bitrix24.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission restrictions on the Bitrix24 account.
- Network connectivity problems preventing API calls.
Error messages:
- Errors thrown during execution will be included in the output if "Continue On Fail" is enabled, showing the error message and timestamp.
- Typical errors relate to failed API calls or missing parameters.
Resolutions:
- Verify that the selected authentication method is correctly configured with valid credentials.
- Ensure the Bitrix24 account has sufficient permissions to access telephony and SIP connector data.
- Check network connectivity and retry if transient errors occur.