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 its Calendar resource. The "Delete Section" operation enables users to delete a calendar section by specifying its unique Section ID. This is useful for automating calendar management tasks such as cleaning up unused or obsolete calendar sections within Bitrix24.
Practical examples include:
- Automatically removing calendar sections that are no longer needed after project completion.
- Cleaning up calendar data during synchronization or migration processes.
- Managing calendar organization dynamically based on business rules.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Section ID | The unique identifier of the calendar section to be deleted. |
| Options | Additional optional parameters: |
| - Access Token | Use a specific access token instead of the one from credentials. |
| - Filter | JSON-formatted filter criteria (not typically used in delete but available). |
| - Order | JSON-formatted sort order (not typically used in delete but available). |
Output
The node outputs an array of items where each item contains a json object representing the result of the deletion operation. If successful, the output will confirm the deletion; if an error occurs, the output includes an error message and metadata such as the resource name and timestamp.
No binary data output is involved in this operation.
Example output JSON snippet on failure:
{
"error": "Error message here",
"resource": "calendar",
"timestamp": "2024-06-01T12:00:00.000Z"
}
Dependencies
- Requires valid authentication with Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Relies on Bitrix24 API endpoints for calendar management.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent Section ID causing the deletion to fail.
- Network connectivity problems preventing API calls.
Error messages:
- Authorization errors: Ensure the API key, OAuth2 token, or webhook URL is correctly configured and has sufficient permissions.
- "Section not found" or similar: Verify the Section ID is correct and exists in the Bitrix24 calendar.
- Generic API errors: Check Bitrix24 service status and network connectivity.
Resolution tips:
- Refresh or reauthenticate credentials if authorization fails.
- Double-check input Section ID for typos or outdated values.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.