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 interaction with its Disk resource to download files. The "Download File" operation allows users to retrieve a file stored in Bitrix24 by specifying its unique file ID. This is useful for automating workflows that require fetching documents, images, or other file types from Bitrix24 storage and using them downstream in automation processes.
Practical examples include:
- Automatically downloading contract PDFs from Bitrix24 when a deal reaches a certain stage.
- Fetching user-uploaded images or reports for processing or archival.
- Integrating Bitrix24 file storage with external systems by retrieving files on demand.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| File ID | The unique identifier of the file to be downloaded from Bitrix24 Disk. |
| Options | Additional optional parameters: - Filter: JSON object to filter results (not typically used for download). - Order: JSON object to specify sort order. - Start: Number indicating start position for pagination (mostly relevant for listing operations). |
Output
The node outputs the downloaded file data in the json output field. Typically, this will contain metadata about the file and the file content itself. If the file is binary (e.g., PDF, image), the node will provide the binary data accordingly so it can be used in subsequent nodes (e.g., saving to disk, sending via email).
json: Contains metadata such as file ID, name, size, and other attributes returned by Bitrix24.binary: Contains the actual file content in binary form, allowing further processing or saving.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's REST API endpoints for file retrieval.
- Proper configuration of credentials in n8n is necessary to authenticate API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or non-existent File ID causing "file not found" errors.
- Network connectivity problems preventing API communication.
Error messages:
- Authorization errors: Check that the selected authentication method is correctly configured and tokens are valid.
- File not found: Verify the File ID is correct and the file exists in Bitrix24 Disk.
- JSON parsing errors in options: Ensure that any JSON input for filters or ordering is well-formed.
Resolutions:
- Re-authenticate or update credentials if authorization fails.
- Double-check File ID values.
- Validate JSON syntax in options fields before execution.