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 node provides integration with the Bitrix24 platform, enabling interaction with various Bitrix24 resources including CRM entities and chatbots. Specifically, for the Chatbot resource and the Delete Chat User operation, this node allows you to remove a user from a specific chat managed by a chatbot in Bitrix24.
This operation is useful in scenarios where you want to programmatically manage chat participants, such as removing users who no longer should have access to a chat or automating chat membership management based on external triggers.
Practical example:
- Automatically removing a user from a customer support chat after their issue is resolved.
- Managing chat memberships dynamically in team collaboration bots.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: OAuth2 (recommended), Webhook URL, or API Key |
| Bot ID | The unique identifier of the chatbot managing the chat |
| Chat ID | The unique identifier of the chat from which the user will be removed |
| User ID | The unique identifier of the user to delete from the chat |
| Options | Additional optional parameters that can be provided (not specifically used in this operation but available for other chatbot operations) |
Details on Authentication options:
- OAuth2: Recommended for production environments; uses OAuth2 tokens for secure API access.
- Webhook: Simpler method using a webhook URL but less secure.
- API Key: Uses an API key credential for authentication.
Output
The output of the node is a JSON object representing the result of the delete user operation. If successful, it typically contains confirmation data from Bitrix24 about the removal of the user from the chat.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message, the resource name ("chatbot"), and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints for chat user management.
- Proper configuration of the Bitrix24 credentials in n8n is necessary.
- Network connectivity to Bitrix24 API endpoints is required.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect Bot ID, Chat ID, or User ID causing "not found" or similar errors.
- Insufficient permissions for the authenticated user to modify chat memberships.
- Network or API rate limiting issues.
Error messages and resolutions:
"error": "Invalid credentials": Check and refresh your authentication tokens or API keys."error": "User not found in chat": Verify the User ID and Chat ID are correct and that the user is currently a member of the chat."error": "Access denied": Ensure the authenticated bot or user has sufficient permissions to remove users from the chat.- Network timeouts or connection errors: Confirm network connectivity and Bitrix24 service status.
Enabling "Continue On Fail" in the node settings can help handle errors gracefully in workflows.