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 integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, the Chatbot - Update Message operation allows users to update an existing chatbot message by specifying the message ID and new text content along with optional parameters such as attachments or keyboard buttons.
This operation is useful in scenarios where a chatbot message needs to be edited after sending, for example:
- Correcting typos or updating information in a previously sent message.
- Changing message content dynamically based on user interaction or external events.
- Modifying message appearance or adding interactive elements like buttons.
Practical example: A customer support chatbot sends a message with initial information but later updates it with additional details or corrections without sending a new message, keeping the chat clean and coherent.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API. Options: OAuth2 (recommended), Webhook URL (simpler but less secure), API Key authentication. |
| Bot ID | The unique identifier of the chatbot whose message is being updated. |
| Message Text | The new text content to replace the existing message's text. |
| Message ID | The unique identifier of the message to update. |
| Options | Additional optional parameters to customize the update request: - Client ID: Identifier for the client making the request. - Open Line ID: Identifier for open communication line. - Language ID: Language code. - Bot Description: Description text for the bot. - Bot Avatar: URL to the bot's avatar image. - Command Description: Description of a command. - Is Common: Boolean flag indicating if the command is common. - Is Hidden: Boolean flag indicating if the command is hidden. - Allow Extranet: Boolean flag to allow extranet access. - Message Type: Type of message, either "Text" or "System". - Attachments: JSON array describing message attachments. - Keyboard Buttons: JSON array defining keyboard layout. - URL Preview: Boolean to enable/disable URL preview. - Custom Parameters: JSON object for any additional custom parameters. - Access Token: Token string for authentication override. |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 after processing the update message request. The exact structure depends on the Bitrix24 API response but typically includes confirmation of the updated message or error details.
If the operation fails and "Continue On Fail" is enabled, the output will contain an item with an error field describing the failure, along with the resource name and timestamp.
The node does not output binary data for this operation.
Dependencies
- Requires connection to Bitrix24 API via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to Bitrix24 endpoints is necessary.
- The node relies on internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Bot ID or Message ID leading to "not found" errors.
- Malformed JSON in attachments, keyboard buttons, or custom parameters causing request rejection.
- Insufficient permissions for the authenticated user or bot to update messages.
Error Messages:
"error": "Invalid authentication": Check that the API key, OAuth token, or webhook URL is correct and has not expired."error": "Message not found": Verify the Message ID corresponds to an existing message sent by the specified bot."error": "Malformed JSON": Ensure all JSON fields (attachments, keyboardButtons, customParameters) are valid JSON strings."error": "Access denied": Confirm the bot has permission to update messages in the target chat or channel.
Resolution Tips:
- Re-authenticate or refresh credentials if tokens expire.
- Double-check IDs and JSON formatting before execution.
- Enable "Continue On Fail" to handle errors gracefully in workflows.