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 and the "Get Sharing Rights" operation, it retrieves sharing permissions for a specified file or folder within the Bitrix24 disk storage. This is useful when you need to programmatically check who has access to certain files or folders in your Bitrix24 environment.
Common scenarios include:
- Auditing file/folder sharing settings in Bitrix24.
- Automating compliance checks on shared documents.
- Integrating Bitrix24 file sharing info into other workflows or systems.
Example: You want to get the list of users or groups that have access rights to a particular document stored in Bitrix24 Disk before sending it externally.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API calls: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Item ID | The unique identifier of the file or folder in Bitrix24 Disk whose sharing rights you want to retrieve. This is required. |
| Options | Additional optional parameters: - Filter: JSON object to filter sharing rights. - Order: JSON object to specify sorting order. - Start: Number indicating pagination start position. |
Output
The node outputs an array of items where each item's json property contains the sharing rights information for the specified file or folder. The exact structure depends on the Bitrix24 API response but typically includes details about users or groups with access and their permission levels.
If binary data were involved (not indicated here), it would represent file content or attachments, but this operation focuses on metadata about sharing rights only.
Dependencies
- Requires a valid Bitrix24 authentication method configured in n8n: OAuth2 credentials, webhook URL, or API key.
- Uses Bitrix24 REST API endpoints internally to fetch sharing rights.
- No additional external dependencies beyond standard Bitrix24 API access.
Troubleshooting
- Invalid or missing Item ID: Ensure the "Item ID" corresponds to an existing file or folder in Bitrix24 Disk.
- Authentication errors: Verify that the selected authentication method is correctly set up and authorized.
- API rate limits or connectivity issues: Check network connectivity and Bitrix24 API usage limits.
- Malformed JSON in Filter or Order options: Validate JSON syntax if using these optional fields.
- If the node returns an error message, it will be included in the output JSON under the
errorfield when "Continue On Fail" is enabled.