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
The node integrates with the Bitrix24 platform, specifically allowing interaction with its telephony features. The "Update External Line" operation under the Telephony resource enables users to update details of an external phone line configured in Bitrix24. This is useful for managing telephony lines dynamically, such as renaming a line or changing its associated number without manual intervention in the Bitrix24 interface.
Practical scenarios include:
- Automatically updating external line information when organizational changes occur.
- Synchronizing telephony line data from other systems into Bitrix24.
- Managing multiple telephony lines programmatically in large deployments.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Line ID | The unique identifier of the external line to update. |
| Line Name | The new name to assign to the external line. |
| Line Number | The new phone number to assign to the external line. |
Output
The node outputs JSON data representing the result of the update operation on the external line. This typically includes confirmation of the updated line's details or any error messages if the update failed.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an object containing:
error: The error message.resource: The resource name ("telephony").timestamp: The ISO timestamp when the error occurred.
No binary data output is indicated for this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints for telephony management.
- Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Line ID leading to "line not found" errors.
- Insufficient permissions in Bitrix24 account to modify telephony lines.
- Network connectivity issues preventing API communication.
Error messages:
- Errors returned by Bitrix24 API will be surfaced in the node output under the
errorfield if "Continue On Fail" is enabled. - Authentication errors suggest checking and renewing credentials.
- Validation errors indicate missing or malformed input properties like Line ID, Line Name, or Line Number.
- Errors returned by Bitrix24 API will be surfaced in the node output under the
Resolutions:
- Verify and refresh authentication tokens or keys.
- Confirm the Line ID exists and is correct.
- Ensure the user account has telephony management rights.
- Check network access and proxy settings if applicable.