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 management operations such as uploading files to Bitrix24's storage. The "Upload File" operation under the "File" resource allows users to upload a file by specifying its name, content, and target folder within Bitrix24.
Common scenarios for this node include:
- Automating document uploads to Bitrix24 from other systems or workflows.
- Storing generated reports or exports directly into Bitrix24 folders.
- Integrating file attachments into CRM records or projects managed in Bitrix24.
For example, a user could automate uploading a PDF invoice generated in another system directly into a specific Bitrix24 folder for record keeping.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key. |
| Folder ID | ID of the destination folder in Bitrix24 where the file will be uploaded. Leave empty for root. |
| File Name | The name to assign to the uploaded file. |
| File Content | The content of the file to upload. For binary files, this should be base64 encoded. |
| Options | Additional optional settings: |
| - Generate Unique Name | If true, generates a unique filename if a file with the same name already exists. |
| - Rights | JSON object defining access rights for the uploaded file. |
| - Access Token | Optional access token string for authentication override. |
Output
The node outputs an array of items, each containing a json property with details about the uploaded file. This typically includes metadata returned by Bitrix24 after a successful upload, such as file ID, name, size, and possibly URLs or paths.
If the node supports binary data output (not explicitly shown here), it would represent the uploaded file or related binary content accordingly.
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 perform file uploads.
- No additional external dependencies beyond Bitrix24 API access are required.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
- Invalid Folder ID: If the folder ID does not exist or is incorrect, the upload will fail. Verify the folder ID or leave empty to upload to root.
- File content issues: For binary files, ensure the content is properly base64 encoded; otherwise, the upload may result in corrupted files.
- Name conflicts: If a file with the same name exists and "Generate Unique Name" is false, the upload might overwrite or fail depending on Bitrix24 behavior.
- API limits or permissions: Insufficient permissions or API rate limits can cause errors. Check Bitrix24 user permissions and API usage quotas.
Common error messages usually contain the API error message from Bitrix24, which can guide resolution steps such as fixing authentication, correcting parameters, or adjusting permissions.