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 providing access to telephony-related resources. The "Get External Line" operation retrieves details about a specific external telephony line by its ID. This is useful in scenarios where you need to fetch configuration or status information about external phone lines connected to your Bitrix24 telephony system.
Practical examples include:
- Fetching details of an external line before updating or deleting it.
- Retrieving line information for reporting or monitoring purposes.
- Integrating telephony line data into workflows that automate call routing or logging.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| Line ID | The unique identifier of the external telephony line to retrieve |
Output
The node outputs JSON data representing the details of the requested external line. The exact structure depends on the Bitrix24 API response but typically includes properties such as line configuration, status, and metadata.
If the node supports binary data output (not indicated here), it would represent related telephony assets or media, but this operation primarily returns JSON data.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Needs network access to the Bitrix24 API endpoints.
- No additional external services are required beyond Bitrix24 itself.
Troubleshooting
Common issues:
- Invalid or missing Line ID parameter will cause the operation to fail.
- Authentication failures due to incorrect or expired credentials.
- Network connectivity problems preventing API calls.
- Insufficient permissions in Bitrix24 account to access telephony line data.
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 "Line not found", "Unauthorized", or "Invalid authentication".
- Errors returned from Bitrix24 API will be included in the output JSON under an
Resolutions:
- Verify the Line ID is correct and exists in Bitrix24.
- Ensure authentication credentials are properly configured and valid.
- Check network connectivity and firewall settings.
- Confirm user permissions in Bitrix24 allow telephony line access.