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 Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, the "Open Lines" resource with the "Finish Session" operation allows users to programmatically close or finish an open communication session within Bitrix24's Open Lines feature. This is useful in scenarios such as automating customer support chat session closures after issue resolution or when a conversation needs to be programmatically ended based on workflow logic.
Practical examples include:
- Automatically finishing a live chat session once a support ticket linked to it is resolved.
- Closing sessions that have been inactive for a certain period.
- Integrating with other systems to mark conversations as finished when external conditions are met.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Options | Additional optional parameters: - Filter: JSON object to filter results - Sort: JSON object to specify sort order |
Note: The "Options" property is shown only when the resource is "openLines". It allows specifying filtering and sorting criteria in JSON format, which can refine the operation behavior.
Output
The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to finish the session. If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with keys:
error: The error message string.resource: The resource name ("openLines").timestamp: ISO timestamp of when the error occurred.
No binary data output is indicated by the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- The node depends on internal helper functions to make API calls to Bitrix24.
- Proper credentials must be configured in n8n for the chosen authentication method.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
- Common issues:
- Incorrect or expired authentication credentials leading to authorization errors.
- Malformed JSON in the "Filter" or "Sort" options causing API call failures.
- Network connectivity problems preventing API requests.
- Error messages:
- Errors thrown during execution will include the message from Bitrix24 API or internal exceptions.
- When "Continue On Fail" is enabled, errors are returned in the output JSON for easier debugging.
- Resolutions:
- Verify and refresh authentication credentials.
- Validate JSON syntax in filter and sort fields.
- Check network connectivity and Bitrix24 service status.
Links and References
- Bitrix24 Open Lines Documentation
- Bitrix24 REST API Reference
- n8n Documentation (for general Bitrix24 node usage)