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, enabling automation workflows to interact with various Bitrix24 resources. Specifically, for the "Open Lines" resource and the "Transfer Session" operation, it facilitates transferring a chat or communication session within Bitrix24's Open Lines feature. This is useful in scenarios where customer support sessions need to be reassigned or escalated to different agents or departments.
Practical examples include:
- Automatically transferring a live chat session to a specialized support team based on customer input.
- Reassigning open communication lines when an agent becomes unavailable.
- Routing sessions dynamically based on business rules implemented in n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Options | Additional parameters for filtering and sorting results. Contains: - Filter: JSON object specifying filter criteria. - Sort: JSON object specifying sort order. |
Note: The "Options" property is shown only when the resource is "openLines".
Output
The node outputs an array of items, each containing a json field with the response data from Bitrix24 after processing the requested operation. For the "Transfer Session" operation, this typically includes confirmation details about the session transfer, such as success status or error messages.
If an error occurs and the node is configured to continue on failure, the output item will contain an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated by the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Uses internal helper functions to make standardized API calls to Bitrix24 endpoints.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrectly formatted filter or sort JSON causing API request failures.
- Network connectivity problems preventing API calls.
Error messages:
- Errors thrown during execution will include the message returned by Bitrix24 or generated internally.
- If "Continue On Fail" is enabled, errors are returned in the output JSON under the
errorkey.
Resolution tips:
- Verify that the selected authentication method is correctly configured and active.
- Ensure JSON inputs for filters and sorting are valid and conform to Bitrix24 API expectations.
- Check network connectivity and Bitrix24 service status.