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 enabling operations on various Bitrix24 resources. For the Telephony resource and the Finish External Call operation, it allows users to programmatically finish an external call by specifying the call's unique identifier. This is useful in scenarios where calls are managed outside of Bitrix24 but need to be synchronized or finalized within the Bitrix24 telephony system.
Practical examples include:
- Automatically ending a call in Bitrix24 after it has been completed in an external telephony system.
- Synchronizing call status between third-party call centers and Bitrix24 CRM.
- Triggering workflows or logging activities in Bitrix24 once an external call finishes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler, less secure), or API Key authentication. |
| Call ID | The unique identifier of the external call that you want to finish in Bitrix24. |
Output
The node outputs JSON data representing the result of the requested operation. For the "Finish External Call" operation, the output JSON typically contains confirmation or details about the finished call as returned by the Bitrix24 API.
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.
The node does not explicitly handle binary data for this operation.
Dependencies
- Requires access to the Bitrix24 platform via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Proper credentials must be configured in n8n corresponding to the chosen authentication method.
- Network connectivity to Bitrix24 API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent Call ID will result in errors from the Bitrix24 API.
- Network issues or API rate limits may cause request failures.
Error messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield. - If the node is set to continue on failure, it returns the error information without stopping the workflow.
- To resolve errors, verify the Call ID correctness, ensure valid credentials, and check network connectivity.
- Errors returned from Bitrix24 API will be included in the output JSON under the