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 Add Section operation, this node enables users to add a new calendar section by providing the section data in JSON format.
This functionality is useful when automating calendar management within Bitrix24, such as creating new calendar sections programmatically based on workflow triggers or external events. For example, a user might automatically create a new calendar section for a project team whenever a new project is initiated in their system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| Section Data | JSON-formatted data describing the calendar section to add. This is required and must be valid JSON. |
| Options | Additional optional parameters: |
| - Access Token | A specific access token string to override the one from credentials. |
| - Filter | JSON-formatted filter criteria (not typically used for adding a section). |
| - Order | JSON-formatted sort order (not typically used for adding a section). |
Output
The node outputs an array of items where each item contains a json object representing the result of the operation. For the Add Section operation, the output JSON will typically include details about the newly created calendar section, such as its ID and properties as returned by the Bitrix24 API.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with fields:
error: The error message.resource: The resource name ("calendar").timestamp: The ISO timestamp when the error occurred.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to a Bitrix24 instance.
- Supports three authentication methods: OAuth2, Webhook URL, or API Key.
- Requires appropriate credentials configured in n8n for the chosen authentication method.
- Uses Bitrix24 API endpoints internally via a generic resource handler factory.
Troubleshooting
Common Issues:
- Invalid or malformed JSON in the "Section Data" property can cause API errors.
- Incorrect or expired authentication tokens will lead to authorization failures.
- Insufficient permissions in Bitrix24 to create calendar sections may cause errors.
Error Messages:
- Errors returned from Bitrix24 API are surfaced in the node's output if "Continue On Fail" is enabled.
- Common error messages include authentication failures, invalid input data, or permission denied.
Resolutions:
- Validate JSON syntax before running the node.
- Ensure that the authentication credentials are correct and have not expired.
- Verify that the authenticated user has rights to create calendar sections in Bitrix24.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Calendar API Reference
- n8n Documentation on Credentials
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.