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 allowing users to manage telephony external lines. The "Delete External Line" operation enables the removal of a specified external telephony line from the Bitrix24 system.
Common scenarios for this node include:
- Automating cleanup of unused or obsolete external phone lines in Bitrix24.
- Managing telephony resources dynamically based on business workflows.
- Integrating telephony management into broader CRM or communication automation processes.
For example, a user might set up an automation that deletes an external line when a related project or campaign ends, ensuring telephony resources are kept tidy and costs minimized.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler but less secure), API Key authentication. |
| Line ID | The unique identifier of the external telephony line to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the deletion operation. If successful, the output typically confirms the deletion status or returns relevant metadata from Bitrix24 about the deleted line.
If an error occurs and the node is configured to continue on failure, 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 involved in 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 telephony API endpoints to perform the deletion.
- Proper configuration of credentials within n8n is necessary to authorize API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent Line ID will result in errors indicating the line could not be found.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the
errorfield if "Continue On Fail" is enabled. - Typical messages include authentication failures, invalid parameters, or permission denials.
- Errors returned from Bitrix24 API will be surfaced in the
Resolutions:
- Verify and refresh authentication credentials.
- Double-check the Line ID value for correctness.
- Ensure the Bitrix24 account has sufficient permissions to delete telephony lines.
- Confirm network access to Bitrix24 API endpoints.