Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 CRM and business resources. Specifically, for the Chat resource with the Delete Message operation, it enables deleting a chat message within Bitrix24.

Common scenarios where this node is beneficial include:

• Automating cleanup of chat messages in Bitrix24 after certain triggers or workflows.
• Managing chat content programmatically as part of customer support or internal communication automation.
• Integrating Bitrix24 chat management into broader business process automations.

For example, you could use this node to automatically delete outdated or sensitive chat messages after processing them elsewhere, ensuring compliance or data hygiene.

Properties

Note: The node also requires selecting the Resource ("Chat" in this case) and the Operation ("Delete Message"), but these are fixed by your selection.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the message was successfully deleted or provide error details if the deletion failed.

If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is indicated for this operation.

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 to perform operations.
• No additional external services beyond Bitrix24 are required.
• Proper configuration of credentials in n8n is necessary for successful execution.

Troubleshooting

• Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
• API call failures: Network issues or incorrect permissions in Bitrix24 may cause API calls to fail. Verify API access rights.
• Invalid message ID or resource parameters: Make sure the message ID to delete exists and the resource/operation parameters are correctly set.
• Error messages in output: If the node returns an error JSON, check the error message for clues. Common errors include permission denied, message not found, or invalid authentication.
• Continue on Fail behavior: If enabled, errors won't stop the workflow but will be returned in the output JSON for handling downstream.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 Chat API Reference
• n8n Documentation on Credentials

This summary is based solely on static analysis of the provided source code and property definitions.