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
This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Chat resource with the Update Message operation, it enables updating an existing chat message within Bitrix24.
Common scenarios where this node is beneficial include:
- Automating updates to chat messages based on external triggers or workflows.
- Synchronizing chat content with other systems or databases.
- Correcting or appending information in chat messages programmatically.
For example, a user might use this node to update a customer support chat message with additional details after processing a ticket in another system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
Note: The node also supports selecting the Resource and Operation, but since the focus is on the Chat resource and Update Message operation, those are implicitly set.
Output
The node outputs an array of items corresponding to the processed data from Bitrix24. Each item contains a json field with the response data from the Bitrix24 API related to the updated chat message.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with a json object including:
error: The error message string.resource: The resource name ("chat" in this context).timestamp: ISO timestamp of when the error occurred.
The node does not explicitly mention binary data output, so it primarily returns JSON structured data representing the updated message or error details.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API Key authentication.
The node depends on Bitrix24's REST API endpoints to perform operations.
No additional external services beyond Bitrix24 are required.
Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common Issues:
- Incorrect or expired authentication credentials leading to authorization errors.
- Insufficient permissions in Bitrix24 account to update chat messages.
- Invalid message IDs or resource identifiers causing API call failures.
- Network connectivity issues preventing access to Bitrix24 API.
Error Messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages may include authentication failures, permission denials, or invalid parameters.
Resolution Tips:
- Verify that the selected authentication method is correctly configured and valid.
- Ensure the Bitrix24 user has rights to update chat messages.
- Double-check input parameters such as message IDs.
- Test connectivity to Bitrix24 API endpoints outside n8n to isolate network issues.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions.