Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and disk files. Specifically, for the Disk resource and the Delete File operation, it enables deleting a file stored in Bitrix24's disk storage by specifying its file ID.

Common scenarios where this node is beneficial include:

• Automating cleanup of outdated or temporary files in Bitrix24.
• Managing file lifecycle within business workflows by programmatically removing files no longer needed.
• Integrating Bitrix24 file management into broader automation pipelines.

For example, after processing a document uploaded to Bitrix24, you might want to delete the original file automatically to save storage space.

Properties

Output

The node outputs an array of items corresponding to the processed input items. Each output item contains a json field with the response from Bitrix24 after attempting the delete operation.

• On success, the output typically includes confirmation details from Bitrix24 about the deletion.
• On failure, if "Continue on Fail" is enabled, the output item will contain an error field with the error message, along with the resource name and a timestamp.

No binary data output is produced by this operation.

Dependencies

• Requires connection to Bitrix24 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 API endpoints is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing File ID: The node requires a valid file ID; ensure the correct ID is provided.
  • Authentication errors: Verify that the selected authentication method is correctly configured and the credentials are valid.
  • Insufficient permissions: The authenticated user or token must have rights to delete files in Bitrix24.
  • Network connectivity problems can cause API call failures.

• Error messages:

  • Errors returned from Bitrix24 API will be included in the output if "Continue on Fail" is enabled.
  • Typical errors include "File not found", "Access denied", or "Invalid authentication".

• Resolution tips:

  • Double-check the file ID and ensure the file exists.
  • Confirm that the API credentials have appropriate permissions.
  • Test the authentication separately to verify connectivity.
  • Enable "Continue on Fail" during testing to capture error details without stopping workflow execution.

Links and References

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