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 file uploads to a specified disk storage and folder within Bitrix24. The "Upload File" operation under the "Disk" resource allows users to upload binary files from n8n workflows directly into Bitrix24's cloud storage.
Common scenarios where this node is beneficial include:
- Automating document management by uploading generated reports or invoices to Bitrix24.
- Syncing files from other systems or sources into Bitrix24 for centralized access.
- Backing up important files or attachments related to CRM entities in Bitrix24.
For example, a workflow could generate a PDF invoice and then use this node to upload it to a designated folder in Bitrix24 Disk for easy sharing and archival.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Storage ID | The identifier of the Bitrix24 storage where the file will be uploaded. |
| Folder ID | The identifier of the folder inside the storage where the file will be placed. |
| Binary Property | The name of the binary property in the input data that contains the file to upload (e.g., "data"). |
| File Name | Optional custom name for the uploaded file; if not provided, the original file name is used. |
| Options - Filter | JSON object specifying filter criteria (not typically used for upload but available as an option). |
| Options - Order | JSON object specifying sort order (not typically used for upload but available as an option). |
| Options - Start | Number indicating start position for pagination (not typically used for upload but available as an option). |
Output
The node outputs an array of items corresponding to the processed inputs. Each itemβs json field contains the response data from Bitrix24 after uploading the file. This typically includes metadata about the uploaded file such as its ID, name, size, and storage location.
If the node processes multiple input items, each output item corresponds to one uploaded file.
Binary data is consumed as input (the file to upload) but the node does not output binary data itself.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24 API endpoints for disk storage operations.
- Proper configuration of authentication credentials in n8n is necessary.
- Network connectivity to Bitrix24 services is required.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 is recommended for production environments.
- Invalid Storage or Folder IDs: Verify that the provided storage and folder IDs exist and are accessible with the authenticated user.
- Missing binary property: Confirm that the input data contains the specified binary property with the file content.
- File name issues: If no file name is provided, the node attempts to use the original file name; ensure the binary data has a valid filename.
- API rate limits or network issues: Bitrix24 may throttle requests; handle retries or check network connectivity.
- Error messages: The node returns error details in the output JSON when
continueOnFailis enabled, including the error message, resource, and timestamp.