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, specifically allowing interaction with various Bitrix24 resources such as CRM entities and calendar data. The "Calendar" resource with the "Get Sections" operation enables users to retrieve calendar sections from their Bitrix24 account.
Typical use cases include:
- Fetching calendar sections to display or synchronize calendars in external applications.
- Automating workflows that depend on calendar availability or structure within Bitrix24.
- Integrating Bitrix24 calendar data into broader business processes managed via n8n.
For example, a user might want to list all calendar sections before creating events or assigning tasks to specific calendar sections programmatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended for production), Webhook (simpler but less secure), or API Key authentication. |
| Options | Collection of optional parameters: |
| Access Token | A specific access token string to override the default credential token. |
| Filter | JSON-formatted filter criteria to narrow down which calendar sections to retrieve. |
| Order | JSON-formatted sorting order to define how the results should be ordered. |
Output
The node outputs an array of items where each item's json property contains the data returned by the Bitrix24 API for calendar sections. This typically includes details about each calendar section such as its ID, name, color, and other metadata defined by Bitrix24.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires a Bitrix24 account with appropriate permissions.
- Requires one of the supported authentication methods configured in n8n credentials: OAuth2, webhook URL, or API key.
- Uses Bitrix24's REST API endpoints internally to fetch calendar sections.
- No additional external dependencies beyond standard HTTP requests to Bitrix24.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens can cause authorization errors.
- Incorrectly formatted JSON in the Filter or Order options may lead to API request failures.
- Insufficient permissions in Bitrix24 for accessing calendar data.
Error messages:
- Errors thrown by the Bitrix24 API are surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, invalid parameters, or network issues.
Resolutions:
- Verify and refresh authentication credentials.
- Ensure JSON inputs for filters and ordering are valid.
- Confirm the Bitrix24 user has rights to access calendar sections.