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 users to interact with various Bitrix24 resources such as CRM entities and chats. Specifically, for the Chat resource with the Get Messages operation, it retrieves messages from a specified chat within Bitrix24.
Typical use cases include:
- Fetching conversation history from a Bitrix24 chat for analysis or record-keeping.
- Integrating Bitrix24 chat messages into other workflows or systems.
- Automating responses or processing chat data in business automation scenarios.
For example, a user might configure this node to pull all messages from a customer support chat to analyze customer inquiries or to trigger follow-up actions based on message content.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Chat ID | The unique identifier of the chat from which to retrieve messages |
Output
The node outputs an array of items where each item contains a json object representing the retrieved data from Bitrix24. For the "Get Messages" operation under the Chat resource, the json output will contain the messages fetched from the specified chat.
If an error occurs and the node is configured to continue on failure, the output will include an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not explicitly handle binary data output.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production environments)
- Webhook URL authentication (simpler but less secure)
- API key authentication
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to the Bitrix24 API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause failures in retrieving messages.
- Incorrect or missing Chat ID will result in errors or empty results.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors thrown by the node will include the error message from the Bitrix24 API or internal processing.
- If "Continue On Fail" is enabled, errors are returned in the output JSON with fields
error,resource, andtimestamp.
Resolution Tips:
- Verify that the authentication credentials are valid and have sufficient permissions.
- Ensure the Chat ID is correct and corresponds to an existing chat.
- Check network connectivity and firewall settings.
- Enable "Continue On Fail" during testing to capture error details without stopping workflow execution.