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 with the Get Voximplant Line operation, it retrieves details about a specific Voximplant line by its ID. This is useful in scenarios where you need to fetch configuration or status information about a telephony line integrated via Voximplant within Bitrix24.
Practical examples include:
- Fetching line details to display or log call routing configurations.
- Validating if a particular Voximplant line exists before performing further telephony actions.
- Integrating telephony data into CRM workflows or dashboards.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Line ID | The unique identifier of the Voximplant line to retrieve. This is required for the operation. |
Output
The node outputs JSON data representing the details of the requested Voximplant line. The exact structure depends on the Bitrix24 API response but typically includes properties such as line configuration, status, and related metadata.
If the node supports binary data output (not evident from the provided code), it would represent any associated files or media related to the line, but this is not indicated here.
Dependencies
- Requires an active connection to Bitrix24 with appropriate permissions.
- Needs one of the supported authentication methods configured: OAuth2 token, webhook URL, or API key.
- Relies on Bitrix24's API endpoints for telephony and Voximplant integration.
- No additional external libraries beyond those bundled are required.
Troubleshooting
- Common issues:
- Invalid or missing Line ID will cause the API call to fail.
- Incorrect or expired authentication credentials will result in authorization errors.
- Network connectivity problems can prevent successful API calls.
- Error messages:
- Errors returned from Bitrix24 API will be included in the output JSON under an
errorfield if "Continue On Fail" is enabled. - Typical errors include "Unauthorized", "Line not found", or "Invalid parameters".
- Errors returned from Bitrix24 API will be included in the output JSON under an
- Resolutions:
- Verify that the Line ID is correct and exists in your Bitrix24 account.
- Ensure authentication credentials are valid and have necessary scopes.
- Check network access and proxy/firewall settings if applicable.