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 providing operations related to telephony features such as showing details of an external call. It is useful for workflows that need to retrieve information about phone calls made or received through Bitrix24's telephony system. For example, you can use this node to fetch detailed data about a specific external call by its ID, which can then be used for logging, analytics, or triggering further automation based on call outcomes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Call ID | The unique identifier of the external call you want to show details for. |
Output
The node outputs JSON data representing the details of the specified external call. This typically includes all relevant information returned by the Bitrix24 API about that call, such as call status, duration, participants, timestamps, and any associated metadata. If an error occurs, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires access to a Bitrix24 account with telephony features enabled.
- Requires one of the following authentication methods configured in n8n:
- OAuth2 credentials for Bitrix24 API access.
- A Bitrix24 webhook URL.
- An API key credential for Bitrix24.
- The node depends on internal helper functions to make standard API calls to Bitrix24.
Troubleshooting
- Common issues:
- Invalid or expired authentication credentials may cause authorization errors.
- Providing an incorrect or non-existent Call ID will result in an error or empty response.
- Network connectivity issues can prevent successful API calls.
- Error messages:
- Errors thrown during execution include the error message from the Bitrix24 API or network layer.
- When
continueOnFailis enabled, errors are returned in the output JSON under theerrorproperty.
- Resolutions:
- Verify that the authentication method and credentials are correctly set up and valid.
- Confirm the Call ID exists and is correct.
- Check network connectivity and Bitrix24 service status.