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 allows interaction with the Bitrix24 CRM and business platform. Specifically, for the "Open Lines" resource and the "Start Session" operation, this node initiates a new session in Bitrix24's Open Lines communication channels. This is useful for automating customer support workflows, starting chat sessions, or integrating live communication channels into automated processes.
Practical examples include:
- Automatically starting a chat session when a new lead is created.
- Initiating customer support conversations triggered by external events.
- Integrating Bitrix24 Open Lines sessions into multi-step automation workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| Options | Additional optional parameters to customize the request: |
| - Filter | JSON object specifying filter criteria to narrow down results |
| - Sort | JSON object specifying sorting order for results |
Output
The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to start an Open Lines session. The exact structure depends on Bitrix24's API response but typically includes session details such as session ID, status, timestamps, and any error messages if applicable.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with a json containing:
error: The error message string.resource: The resource name ("openLines").timestamp: ISO timestamp of the error occurrence.
No binary data output is indicated.
Dependencies
- Requires authentication credentials for Bitrix24 via one of these methods:
- OAuth2 token credential
- Webhook URL credential
- API key credential
- Uses internal helper functions to make API calls to Bitrix24.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Incorrect or expired authentication credentials will cause API call failures.
- Malformed JSON in the "Filter" or "Sort" options may cause errors.
- Network connectivity issues can prevent successful API requests.
Error messages:
- Errors thrown during execution are caught and returned in the output if "Continue On Fail" is enabled.
- Typical error messages relate to authentication failure, invalid parameters, or API rate limits.
Resolutions:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure JSON inputs for filters and sorting are well-formed.
- Check network connectivity and Bitrix24 service status.