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 integrates with the Bitrix24 CRM and business platform, enabling users to interact with various resources such as calendars, CRM entities, and more. Specifically, the Calendar - Get Accessibility operation checks the availability of specified users or groups within a given date range. This is useful for scheduling meetings or events by determining when participants are free.
Typical use cases include:
- Checking user or group calendar availability before booking meetings.
- Automating event scheduling workflows based on participant accessibility.
- Integrating Bitrix24 calendar data into broader automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| Type | Type of calendar to query: User, Group, or Company calendar. |
| Owner ID | Identifier of the calendar owner whose availability is being checked. |
| From Date | Start datetime for the accessibility check period. |
| To Date | End datetime for the accessibility check period. |
| Users | Comma-separated list of user IDs to check accessibility for (optional). |
| Options | Additional optional parameters: |
| Access Token | Override the default credential token with a specific access token. |
| Filter | JSON object specifying filter criteria for the request. |
| Order | JSON object specifying sort order for the results. |
Output
The node outputs an array of items where each item's json property contains the accessibility information retrieved from Bitrix24 for the specified calendar type and owner within the requested date range. The exact structure depends on the Bitrix24 API response but generally includes details about free/busy times or available slots.
If binary data were involved (not indicated here), it would represent attachments or files related to calendar events, but this operation focuses on JSON data only.
Dependencies
- Requires valid authentication credentials configured in n8n using one of the supported methods: OAuth2, webhook URL, or API key.
- Access to Bitrix24 API endpoints for calendar and user/group data.
- Proper permissions in Bitrix24 to read calendar accessibility information.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured and the credentials are valid.
- Invalid Owner ID or User IDs: Verify that the provided IDs exist in Bitrix24 and have accessible calendars.
- Date range issues: The "From Date" must be earlier than the "To Date"; otherwise, the API may return errors or empty results.
- API rate limits or connectivity problems: May cause failures; check network connectivity and Bitrix24 API status.
- Malformed JSON in Filter or Order options: Ensure these fields contain valid JSON syntax to avoid parsing errors.