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 interacts with the Bitrix24 platform, specifically enabling operations on various Bitrix24 resources. For the Chatbot resource and the Update Chat Title operation, it updates the title of a specified chat within Bitrix24. This is useful for automating chat management tasks such as renaming group chats or channels programmatically based on workflow events.
Practical examples include:
- Automatically updating chat titles to reflect project status changes.
- Renaming support chat groups dynamically based on ticket priority or customer information.
- Standardizing chat names across teams using automated workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key authentication. |
| Bot ID | The unique identifier of the chatbot performing the operation. |
| Chat ID | The unique identifier of the chat whose title will be updated. |
| Title | The new title to assign to the chat. |
| Options | Additional optional parameters that can be provided, including: |
| - Client ID | Identifier for the client making the request. |
| - Open Line ID | Identifier for the open line (communication channel). |
| - Language ID | Language code for localization purposes. |
| - Bot Description | Description text for the bot. |
| - Bot Avatar | URL pointing to the bot's avatar image. |
| - Command Description | Description of a command 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 access. |
| - Message Type | Type of message, either "Text" or "System". |
| - Attachments | JSON array describing attachments to include. |
| - Keyboard Buttons | JSON array defining keyboard layout/buttons. |
| - URL Preview | Boolean flag 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 where each item contains a json property representing the response from Bitrix24 after attempting to update the chat title. If an error occurs and the node is configured to continue on failure, the output includes an error message along with the resource name and a timestamp.
No binary data output is indicated.
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 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 permission errors.
- Insufficient permissions for the authenticated user or bot to update chat titles.
- Malformed JSON in options like attachments or keyboard buttons causing request failures.
Error Messages:
- Errors returned by Bitrix24 API are surfaced in the output under the
errorfield. - Typical errors include authentication failures, invalid parameters, or API rate limits.
- Errors returned by Bitrix24 API are surfaced in the output under the
Resolutions:
- Verify and refresh authentication credentials.
- Confirm Bot ID and Chat ID values are correct and accessible.
- Ensure the bot has appropriate permissions in Bitrix24.
- Validate JSON structures in optional fields before execution.