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 platform, specifically enabling operations on various Bitrix24 resources. The "Chatbot" resource with the "Delete Message" operation allows users to delete a specific message sent by a chatbot within Bitrix24's messaging environment.
Typical use cases include:
- Automating cleanup of outdated or incorrect chatbot messages.
- Managing chatbot conversations programmatically by removing messages based on workflow logic.
- Moderation scenarios where certain chatbot messages need to be retracted automatically.
For example, after sending a notification message via a chatbot, a workflow might decide to delete that message if a condition changes, such as a deal being closed or a lead status updated.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used for authenticating API requests. Options: OAuth2 (recommended), Webhook, API Key. |
| Bot ID | The unique identifier of the chatbot whose message is to be deleted. |
| Message ID | The unique identifier of the message to delete. |
| Options | Additional optional parameters to customize the 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 | 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 a command is common. |
| - Is Hidden | Boolean flag indicating if a command is hidden. |
| - Allow Extranet | Boolean flag to allow extranet access. |
| - Message Type | Type of the message, either "Text" or "System". |
| - Attachments | JSON array describing attachments associated with the message. |
| - Keyboard Buttons | JSON array defining keyboard layout/buttons for the message. |
| - URL Preview | Boolean to enable or disable URL preview in the message. |
| - Custom Parameters | JSON object for any additional custom parameters. |
| - Access Token | Access token string for authentication (alternative to other auth methods). |
Output
The node outputs an array containing one item per input item processed. Each output item includes a json field with the response from Bitrix24 API regarding the deletion operation.
- On success, the output typically contains confirmation details about the deleted message.
- On failure, if "Continue On Fail" is enabled, the output will contain an error object with fields:
error: Error message string.resource: The resource name ("chatbot").timestamp: ISO timestamp of when the error occurred.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's API endpoints for chatbot message management.
- No additional external libraries beyond those bundled with the node are required.
- Proper configuration of credentials and permissions in Bitrix24 is necessary to perform message deletions.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect Bot ID or Message ID causing "not found" errors.
- Insufficient permissions for the authenticated user or bot to delete messages.
- Malformed JSON in options like attachments or keyboard buttons causing API request failures.
Error Messages:
"error": "Message not found": Verify the Message ID is correct and belongs to the specified Bot ID."error": "Access denied": Check authentication credentials and ensure the bot has rights to delete messages."error": "Invalid authentication": Refresh or reconfigure authentication credentials.- JSON parsing errors: Validate JSON syntax in any JSON-type properties before execution.
Resolution Tips:
- Double-check all IDs and authentication settings.
- Use the Bitrix24 developer console or API documentation to verify endpoint availability.
- Enable "Continue On Fail" during testing to capture error details without stopping workflows.