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 to add events to calendars. It supports adding events to different types of calendars such as user calendars, group calendars, or company-wide calendars. This functionality is useful for automating scheduling tasks, syncing external event data into Bitrix24, or managing organizational calendars programmatically.
Practical examples include:
- Automatically creating calendar events when a new deal or task is created in Bitrix24.
- Syncing events from an external system into a user's Bitrix24 calendar.
- Scheduling company-wide meetings or group events based on triggers from other workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Type | Type of calendar where the event will be added. Options: User, Group, Company calendar. |
| Owner ID | Identifier of the calendar owner (user, group, or company) where the event will be created. |
| Section ID | Identifier of the specific calendar section (optional). |
| Event Data | JSON object containing the details of the event to add (required). |
| Options | Additional optional parameters: - Access Token: override default token - Filter: JSON filter criteria - Order: JSON sort order |
Output
The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to add the event. The exact structure depends on Bitrix24's API response but typically includes details about the created event such as its ID and status.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with fields:
error: Error message stringresource: The resource name ("calendar")timestamp: ISO timestamp of the error occurrence
No binary data output is indicated by the source code.
Dependencies
- Requires valid Bitrix24 credentials configured in n8n, supporting OAuth2, webhook URL, or API key authentication.
- Relies on Bitrix24 API endpoints for calendar event management.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens causing authorization failures.
- Incorrect or missing
ownerIdorsectionIdleading to "not found" errors. - Malformed JSON in
eventDatacausing API request failures.
Error messages:
- Authorization errors: Ensure correct authentication method and valid credentials.
- Validation errors from Bitrix24 API: Check that required event fields are present and correctly formatted.
- Network or API connectivity issues: Verify network access and Bitrix24 service availability.
Enabling "Continue On Fail" allows workflows to handle errors gracefully without stopping execution.