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, the "Chatbot" resource with the "Update Bot" operation enables users to update properties of an existing chatbot within their Bitrix24 environment. This can include changing the bot's description, avatar, language settings, message types, command visibility, and other configuration options.
This node is beneficial in scenarios where automated chatbots need to be managed programmatically, such as updating bot details after deployment, customizing bot behavior dynamically, or integrating chatbot management into broader automation workflows.
Practical examples:
- Updating a chatbot's avatar URL to reflect a new branding image.
- Changing the language ID to support multilingual chatbot interactions.
- Modifying command descriptions or visibility to control user access to certain bot commands.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used for authenticating API requests. Options: OAuth2 (recommended), Webhook, API Key |
| Bot ID | The unique identifier of the chatbot to update (required) |
| Options | Collection of optional parameters to customize the update: |
| - Client ID | Identifier for the client making the request |
| - Open Line ID | Identifier for the open communication line |
| - Language ID | Language code to set the bot's language |
| - Bot Description | Text description of the chatbot |
| - Bot Avatar | URL pointing to the bot's avatar image |
| - Command Description | Description text for a specific command |
| - Is Common | Boolean flag indicating if the command is common |
| - Is Hidden | Boolean flag indicating if the command should be hidden |
| - Allow Extranet | Boolean flag to allow extranet users access |
| - Message Type | Type of message sent by the bot. Options: Text, System |
| - Attachments | JSON array defining attachments to include |
| - Keyboard Buttons | JSON array defining keyboard layout |
| - URL Preview | Boolean flag to enable or disable URL preview |
| - Custom Parameters | JSON object for additional custom parameters |
| - Access Token | Access token string for authentication purposes |
Output
The node outputs an array of items, each containing a json property with the response data from the Bitrix24 API related to the update operation. If an error occurs and the node is configured to continue on failure, the output will contain 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.
- Proper configuration of these credentials within n8n is necessary.
- Network access to the Bitrix24 API endpoints is required.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Bot ID causing "not found" or similar errors.
- Malformed JSON in attachments, keyboard buttons, or custom parameters causing request failures.
- Insufficient permissions for the authenticated user to update chatbot settings.
Error messages:
- Errors returned from the Bitrix24 API will be surfaced in the node's output when "Continue On Fail" is enabled.
- Typical errors include authentication failures, invalid parameters, or API rate limits.
Resolutions:
- Verify that the authentication method and credentials are correctly set up and valid.
- Confirm the Bot ID exists and is correct.
- Validate JSON inputs for proper formatting.
- Ensure the authenticated user has adequate permissions in Bitrix24.