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 Calendar resource with the Get Events operation, it retrieves calendar events from a specified calendar type (User, Group, or Company calendar) within a given date range. This is useful for automating workflows that require fetching scheduled events, meetings, or appointments from Bitrix24 calendars.
Common scenarios include:
- Synchronizing Bitrix24 calendar events with other calendar services.
- Triggering actions based on upcoming events.
- Reporting or analytics on calendar usage and event distribution.
Example: Fetch all user calendar events between two dates to send reminders or update another system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Type | Type of calendar to query: User, Group, or Company calendar. |
| Owner ID | Identifier of the calendar owner (user or group ID). |
| Section ID | Identifier of the specific calendar section (optional). |
| From Date | Start datetime to filter events from. |
| To Date | End datetime to filter events until. |
| Return All | Boolean flag indicating whether to return all matching events or limit the number of results. |
| Max Pages to Load | Maximum number of pages to load when not returning all results; each page contains up to 50 items. |
| Options | Additional optional parameters: |
| - Access Token | Override the default access token with a custom one. |
| - Filter | JSON object specifying filter criteria for querying events. |
| - Order | JSON object specifying sorting order for the returned events. |
Output
The node outputs an array of event objects in the json field. Each event represents a calendar entry retrieved from Bitrix24 according to the specified filters and parameters.
If binary data were involved (e.g., attachments), it would be included in the binary output, but this operation focuses on JSON event data only.
Dependencies
- Requires valid authentication credentials for Bitrix24 via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's API endpoints for calendar event retrieval.
- No additional external dependencies beyond standard n8n credential setup are required.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
- Empty results: Verify that the Owner ID and calendar Type are correct and that the date range (
From DateandTo Date) actually contains events. - Pagination limits: If not returning all results, the
Max Pages to Loadproperty limits how many pages of results are fetched. Increase if needed but beware of API rate limits. - Invalid filter/order JSON: When using the
FilterorOrderoptions, ensure the JSON syntax is correct and matches Bitrix24 API expectations. - API errors: Network issues or Bitrix24 service outages can cause failures; check connectivity and Bitrix24 status.