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 allows interaction with the Bitrix24 CRM and business platform. Specifically, for the Chatbot resource and the Set Chat Owner operation, this node enables setting or changing the owner of a chat within Bitrix24's chat system. This is useful in scenarios where chat ownership needs to be assigned or transferred, such as managing responsibility for customer support chats or internal team communications.
Practical examples include:
- Assigning a specific user as the owner of a group chat to manage notifications and permissions.
- Transferring chat ownership when a team member leaves or changes roles.
- Automating chat ownership assignment based on workflow triggers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Bot ID | The unique identifier of the chatbot involved in the operation. |
| Chat ID | The unique identifier of the chat whose owner is being set. |
| Options | Additional optional parameters that can be provided to customize the request. These include: |
| - Client ID | Identifier for the client making the request. |
| - Open Line ID | Identifier for the open line (communication channel) associated with the chat. |
| - Language ID | Language code to specify localization preferences. |
| - Bot Description | Text description of the bot. |
| - Bot Avatar | URL pointing to the bot's avatar image. |
| - Command Description | Description text for commands related to the bot. |
| - Is Common | Boolean flag indicating if the command is common (shared). |
| - Is Hidden | Boolean flag indicating if the command should be hidden. |
| - Allow Extranet | Boolean flag specifying whether extranet users are allowed access. |
| - Message Type | Type of message sent; options are "Text" or "System". |
| - Attachments | JSON array describing attachments to include in messages. |
| - Keyboard Buttons | JSON array defining keyboard layout/buttons for interactive messages. |
| - URL Preview | Boolean flag to enable or disable URL preview in messages. |
| - Custom Parameters | JSON object for any additional custom parameters to send with the request. |
| - Access Token | Access token string for authentication purposes (if applicable). |
Output
The node outputs an array of items, each containing a json field with the response data from Bitrix24 after processing the request. The exact structure depends on the Bitrix24 API response for setting the chat owner but typically includes confirmation of success or error details.
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 relies on Bitrix24's REST API endpoints to perform operations.
- Proper configuration of credentials in n8n is necessary to authenticate requests.
- Network connectivity to Bitrix24 services is required.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Bot ID or Chat ID causing "not found" or similar errors.
- Insufficient permissions for the authenticated user to change chat ownership.
- Malformed JSON in options like attachments or keyboard buttons causing request failures.
Error Messages:
- Errors returned by Bitrix24 API will be included in the output under the
errorfield if "Continue On Fail" is enabled. - Typical errors include authentication failures, invalid parameters, or permission denials.
- Errors returned by Bitrix24 API will be included in the output under the
Resolutions:
- Verify and refresh authentication credentials.
- Double-check Bot ID and Chat ID values.
- Ensure the authenticated user has appropriate rights in Bitrix24.
- Validate JSON syntax for complex option fields before execution.