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 allows interaction with the Bitrix24 CRM and business platform. Specifically, for the File resource with the Download File operation, it enables users to download a file from Bitrix24 by specifying its unique file ID. This is useful in automation workflows where files stored in Bitrix24 need to be retrieved for processing, backup, or integration with other systems.
Practical examples include:
- Automatically downloading contract documents stored in Bitrix24 when a deal reaches a certain stage.
- Retrieving images or attachments related to CRM contacts for further analysis or storage.
- Integrating Bitrix24 file downloads into document management or archival workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| File ID | The unique identifier of the file to download |
Output
The node outputs the downloaded file data in the json output field. Typically, this will include metadata about the file and the file content itself. If the file is binary (e.g., image, PDF), the node will provide the binary data accordingly, allowing subsequent nodes to handle or save the file.
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 fetch and download files.
- Proper configuration of authentication credentials in n8n is necessary for successful API calls.
Troubleshooting
- Invalid File ID: If the specified File ID does not exist or is incorrect, the node may throw an error indicating the file was not found. Verify the File ID is correct.
- Authentication Errors: Using incorrect or expired credentials will cause authentication failures. Ensure that the OAuth2 token is valid or the API key/webhook URL is correctly configured.
- Permission Issues: The authenticated user must have permission to access the requested file. Lack of permissions will result in authorization errors.
- Network or API Limitations: Temporary network issues or Bitrix24 API rate limits might cause request failures. Retrying after some time or checking API usage quotas can help.
- The node supports "Continue On Fail" mode; if enabled, errors will be returned as part of the output JSON instead of stopping execution.