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 interacts with the Bitrix24 platform, specifically supporting various resources and operations including telephony features. For the Telephony resource and the Get Voximplant SIP Line operation, it retrieves details about a specific Voximplant SIP line by its ID.
Typical use cases include:
- Fetching configuration or status information of a Voximplant SIP line integrated into Bitrix24 telephony.
- Automating telephony management workflows where SIP line details are needed for further processing or decision-making.
- Integrating telephony data into CRM or other business processes within Bitrix24.
Example: A user wants to get the current settings or status of a particular SIP line used for inbound/outbound calls in their Bitrix24 telephony system to display or log this information elsewhere.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key (Bitrix24 API key authentication) |
| Line ID | The unique identifier of the Voximplant SIP line to retrieve information for. This is required. |
Output
The node outputs JSON data representing the details of the requested Voximplant SIP line. The exact structure depends on the Bitrix24 API response but typically includes properties such as line configuration, status, and related metadata.
If an error occurs during execution, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is produced by this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node relies on Bitrix24's REST API endpoints to fetch telephony and SIP line data.
- Proper permissions in Bitrix24 are necessary to access telephony and Voximplant SIP line information.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or non-existent Line ID causing "not found" errors.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield. - If the node is configured to continue on failure, it returns the error info instead of stopping execution.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolutions:
- Verify that the authentication method and credentials are correctly set up and have sufficient permissions.
- Double-check the Line ID value to ensure it corresponds to an existing Voximplant SIP line.
- Ensure network access to Bitrix24 API endpoints is available.