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 Disk resource with the Get File operation, it enables retrieving a file from the Bitrix24 disk storage by its file ID. This is useful in scenarios where you want to automate workflows involving files stored in Bitrix24, such as downloading documents, images, or other media for processing, backup, or integration with other systems.
Practical examples:
- Automatically download an invoice PDF stored in Bitrix24 when a deal reaches a certain stage.
- Retrieve user-uploaded files from Bitrix24 disk to process or archive them externally.
- Integrate Bitrix24 file storage with cloud services by fetching files on demand.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| File ID | The unique identifier of the file to retrieve from Bitrix24 disk. |
| Options | Additional optional parameters: - Filter: JSON object to filter results (not typically used for single file retrieval). - Order: JSON object specifying sort order. - Start: Number indicating pagination start position. |
Output
The node outputs the retrieved file data in the json output field. The exact structure depends on the Bitrix24 API response for the file, typically including metadata about the file such as its name, size, type, and possibly the file content or a URL to download it.
If the node supports binary data output (common for file downloads), the binary data will represent the actual file content, allowing subsequent nodes to use or save the file.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node internally uses Bitrix24 API calls to fetch file information and content.
- No additional external dependencies beyond standard n8n credential setup and network access to Bitrix24 API endpoints.
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 calls.
- Error messages:
- Authorization errors: Check that the provided 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.
- API call failures: Inspect network settings and ensure Bitrix24 API is reachable.
- To resolve, re-authenticate, confirm File ID, and verify network connectivity.