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 business processes. Specifically, for the "Chat" resource with the "Get Chat Users" operation, it retrieves the list of users participating in a particular chat within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating workflows that require fetching chat participants for notifications or logging.
- Synchronizing chat user data with other systems.
- Building custom dashboards or reports based on chat user activity.
For example, a user might use this node to get all users in a sales team chat to send them a summary report automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of JSON objects representing the users in the specified chat. Each object typically contains user details such as user ID, name, and other relevant metadata provided by the Bitrix24 API.
If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object with the following structure:
{
"error": "Error message",
"resource": "chat",
"timestamp": "ISO timestamp"
}
No binary data output is indicated in the source code.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24's REST API endpoints internally.
- The node depends on internal helper functions to make API calls to Bitrix24.
- No additional external services are required beyond Bitrix24 itself.
Troubleshooting
Common issues:
- Incorrect or expired authentication credentials can cause authorization failures.
- Network connectivity problems may prevent API calls from succeeding.
- Insufficient permissions in Bitrix24 for the authenticated user to access chat user data.
Error messages:
- Errors thrown during API calls will be surfaced with their message in the output if "Continue On Fail" is enabled.
- Typical errors include authentication failures, rate limiting, or invalid resource/operation parameters.
Resolution tips:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure the authenticated user has the necessary permissions in Bitrix24.
- Check network connectivity and API endpoint accessibility.
- Enable "Continue On Fail" to capture error details for debugging.