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 interacts with the Bitrix24 platform, specifically providing operations on various resources including the Disk resource. The "Get File Info" operation retrieves metadata and details about a specific file stored in Bitrix24's disk storage by its file ID.
Common scenarios where this node is beneficial include:
- Automating workflows that require checking file properties before processing or moving files.
- Integrating Bitrix24 file management into broader automation pipelines.
- Fetching file metadata to display or log information without downloading the entire file.
Practical example:
- A workflow that triggers when a new file is uploaded to Bitrix24, then uses this node to get detailed info about the file (such as size, creation date, owner) to decide further actions like sharing or archiving.
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 in Bitrix24 Disk for which information is requested. |
| Options | Additional optional parameters: |
| - Filter | JSON object specifying filter criteria to narrow down results (if applicable). |
| - Order | JSON object defining sort order for returned data (if applicable). |
| - Start | Number indicating the start position for pagination of results (default 0). |
Output
The node outputs an array of items, each containing a json property with the file information retrieved from Bitrix24. This typically includes metadata fields such as file name, size, type, creation/modification dates, owner, and other relevant attributes depending on Bitrix24's API response.
If the node supports binary data output (not explicitly shown in the provided code snippet for this operation), it would represent the actual file content or related binary attachments.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch file information.
- Uses internal helper functions and resource handlers bundled within the node implementation to make API calls.
Troubleshooting
Common issues:
- Invalid or missing File ID: Ensure the File ID parameter is correctly set and corresponds to an existing file.
- Authentication errors: Verify that the selected authentication method is properly configured and valid.
- API rate limits or connectivity problems: Check network access and Bitrix24 API usage limits.
Error messages:
- Errors thrown during execution will include the error message from Bitrix24 API or internal processing.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorfield describing the issue.
Resolution tips:
- Double-check input parameters for correctness.
- Confirm credentials and permissions in Bitrix24.
- Review Bitrix24 API documentation for any changes or limitations.