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 integrates with the Bitrix24 platform, specifically enabling operations on various Bitrix24 resources. For the Chatbot resource and the Update Chat Avatar operation, it allows updating the avatar image of a chatbot within a specified chat. This is useful for automating chatbot management tasks such as customizing the bot's appearance in different chats or updating branding dynamically.
Practical scenarios include:
- Automatically changing a chatbotβs avatar based on context or campaign.
- Managing multiple chatbotsβ avatars across different chat groups programmatically.
- Integrating avatar updates into broader workflows that manage chatbot settings.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Bot ID | The unique identifier of the chatbot whose avatar will be updated. |
| Chat ID | The unique identifier of the chat where the chatbot avatar should be updated. |
| Options | Additional optional parameters to customize the update request: |
| - Client ID | Identifier for the client making the request. |
| - Open Line ID | Identifier for the open communication line. |
| - Language ID | Language code for localization purposes. |
| - Bot Description | Text description of the bot. |
| - Bot Avatar | URL pointing to the new avatar image for the bot. |
| - 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 to allow extranet users access. |
| - Message Type | Type of message sent: "text" or "system". |
| - Attachments | JSON array describing attachments to include. |
| - Keyboard Buttons | JSON array defining keyboard layout/buttons. |
| - URL Preview | Boolean to enable or disable URL preview in messages. |
| - Custom Parameters | JSON object for any additional custom parameters. |
| - Access Token | Access token string for authentication (if applicable). |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 after processing the update avatar request. If an error occurs and the node is configured to continue on failure, the output includes an error object with the error message, resource name, and 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 depends on Bitrix24 API endpoints to perform actions.
- Proper configuration of authentication credentials in n8n is necessary.
- 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.
- Malformed URLs in the Bot Avatar property resulting in failed avatar updates.
- Insufficient permissions for the authenticated user to update chatbot settings.
Error messages:
- Errors returned by Bitrix24 API are passed through; typical messages might include authentication failures, invalid parameters, or permission denials.
- If the node is set to continue on fail, errors are included in the output JSON under an
errorfield.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check Bot ID and Chat ID values.
- Ensure the avatar URL is accessible and correctly formatted.
- Confirm the authenticated user has rights to modify chatbot avatars.