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 Sync Events operation, it enables synchronization of calendar events between Bitrix24 and other systems or workflows. This is useful for automating event management, keeping calendars up to date, or integrating Bitrix24 calendar data into broader business processes.
Practical examples include:
- Automatically syncing new or updated events from Bitrix24 to an external calendar application.
- Importing events from other sources into Bitrix24's calendar.
- Triggering workflows based on calendar event changes in Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Options | Collection of optional parameters: |
| - Access Token | Use a specific access token instead of the one from credentials. |
| - Filter | JSON-formatted filter criteria to limit which calendar events are synced. |
| - Order | JSON-formatted sort order to define how events are ordered during synchronization. |
Output
The node outputs an array of items where each item contains a json field representing the synchronized calendar event data retrieved or sent to Bitrix24. The exact structure depends on the Bitrix24 API response for calendar events but typically includes event details such as ID, title, start/end times, attendees, and other metadata.
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this node primarily deals with JSON event data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch and sync calendar events.
- Uses internal helper functions to make authenticated API calls to Bitrix24.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
- API call failures: Check network connectivity and Bitrix24 API availability; verify that the access token or webhook URL has sufficient permissions.
- Invalid filter/order JSON: Make sure the JSON provided in the Filter and Order options is well-formed and matches Bitrix24 API expectations.
- Continue on Fail behavior: If enabled, errors during execution will return error details in the output rather than stopping the workflow.