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 enables interaction with the Bitrix24 CRM and business platform. Specifically, for the Open Lines resource with the Get Messages operation, it retrieves messages from a specified open communication session within Bitrix24's Open Lines feature. This is useful for automating workflows that involve customer support chats or other real-time communication channels managed in Bitrix24.
Typical use cases include:
- Fetching chat messages from an ongoing or past support session to analyze conversation history.
- Integrating chat data into external systems for reporting or follow-up actions.
- Automating responses or triggering workflows based on message content.
Example: Automatically retrieve all messages from a specific open line session after it ends to log the conversation in a helpdesk system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Session ID | The unique identifier of the open line session from which to get messages (required) |
| Options | Additional optional parameters: - Filter: JSON object to filter messages by criteria - Sort: JSON object to specify sorting order |
Output
The node outputs an array of messages retrieved from the specified open line session. Each item in the output contains a json field representing a single message object as returned by the Bitrix24 API. The exact structure depends on the Bitrix24 Open Lines API response but typically includes message text, sender information, timestamps, and message metadata.
If the node encounters an error and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node internally uses Bitrix24 API calls to fetch data; thus, network access to Bitrix24 endpoints is necessary.
- No additional external dependencies beyond standard n8n credential configuration.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials will cause API call failures.
- Incorrect or missing Session ID will result in no messages being returned or errors.
- Malformed JSON in the Filter or Sort options may cause request errors.
Error messages:
- Errors thrown by the Bitrix24 API are propagated. If "Continue On Fail" is off, execution stops with the error.
- When "Continue On Fail" is enabled, errors are returned as part of the output JSON with fields
error,resource, andtimestamp.
Resolution tips:
- Verify authentication credentials and renew tokens if needed.
- Ensure the Session ID corresponds to an existing open line session.
- Validate JSON syntax in filter and sort inputs before running the node.