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 Get File operation, it retrieves a file from Bitrix24 by its unique file ID. This is useful when you need to access or download files stored in Bitrix24, such as documents, images, or attachments related to CRM records.
Common scenarios include:
- Automating retrieval of contract files or invoices stored in Bitrix24.
- Downloading user-uploaded files for processing or backup.
- Integrating Bitrix24 file storage with other systems by fetching files programmatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| File ID | The unique identifier of the file to retrieve from Bitrix24. |
| Options | Additional optional parameters: |
| Access Token | An optional access token string for authentication override. |
Output
The node outputs JSON data representing the retrieved file's metadata and content information. The exact structure depends on the Bitrix24 API response but typically includes fields such as file name, size, type, and URL or binary data reference if downloaded.
If the node supports binary data output (not explicitly shown in the code snippet), it would provide the file content in binary form suitable for further processing or saving.
Dependencies
- Requires valid authentication credentials configured in n8n for Bitrix24 using one of the supported methods (OAuth2, webhook URL, or API key).
- Relies on Bitrix24 API endpoints to fetch file data.
- No additional external libraries beyond those bundled are required.
Troubleshooting
- Invalid File ID: If the provided File ID does not exist or is incorrect, the node will throw an error indicating the file could not be found.
- Authentication Errors: Using incorrect or expired credentials will result in authentication failures. Ensure that the selected authentication method is properly configured and tokens are valid.
- API Rate Limits: Bitrix24 may impose rate limits; excessive requests might cause temporary blocking.
- Continue On Fail: If enabled, the node returns an error object in the output JSON instead of failing the workflow, allowing graceful error handling.