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, allowing users to interact with various Bitrix24 resources such as CRM entities and chats. Specifically, for the Chat resource with the Get Chat operation, the node retrieves detailed information about a specific chat by its ID.
Common scenarios where this node is beneficial include:
- Fetching chat details to display or process within an automation workflow.
- Integrating Bitrix24 chat data into other systems or dashboards.
- Automating responses or actions based on chat metadata.
For example, a user might use this node to get the details of a customer support chat session in Bitrix24 and then trigger follow-up tasks or notifications based on the chat content or participants.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Chat ID | The unique identifier of the chat to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the chat details retrieved from Bitrix24. The exact structure depends on the Bitrix24 API response for the chat entity but typically includes fields such as chat ID, participants, messages summary, timestamps, and other metadata related to the chat.
If the node supports binary data output (not explicitly shown in the provided code), it would typically represent attachments or media associated with the chat, but no explicit binary output handling is visible here.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Uses Bitrix24's REST API endpoints internally to fetch chat data.
- No additional external dependencies beyond standard HTTP requests to Bitrix24 services.
- Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials will cause API call failures.
- Incorrect or missing Chat ID will result in errors or empty responses.
- Network connectivity issues may prevent communication with Bitrix24 API.
Error Messages:
- Errors thrown during execution will include the error message from the Bitrix24 API or network layer.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorfield describing the issue.
Resolutions:
- Verify that the authentication method selected matches the configured credentials.
- Ensure the Chat ID is correct and exists in the Bitrix24 account.
- Check network access and firewall settings to allow outbound requests to Bitrix24.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic import resolution.