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 interacts with the Bitrix24 platform, specifically focusing on managing timeline layout blocks for CRM entities such as Leads, Deals, Contacts, and Companies. The "Delete Layout Blocks" operation under the "Timeline" resource allows users to remove custom or default layout blocks from the timeline of a specified CRM entity.
Common scenarios where this node is beneficial include:
- Cleaning up or customizing the timeline view by removing unnecessary or outdated layout blocks.
- Automating CRM data presentation adjustments based on business rules.
- Integrating Bitrix24 timeline management into broader workflow automations.
For example, a sales automation workflow might delete certain timeline blocks after a deal is closed to declutter the interface for sales representatives.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Entity Type | Type of CRM entity whose timeline layout blocks will be deleted. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the specific CRM entity instance (e.g., a particular Deal or Contact). |
| Options | Additional optional parameters: - Filter: JSON object to specify filter criteria. - Order: JSON object to define sort order. - Start: Number indicating pagination start position. |
Output
The node outputs an array of items corresponding to the result of the delete operation. Each item contains a json field with the response data from Bitrix24 regarding the deletion of layout blocks.
If an error occurs and the node is configured to continue on failure, the output includes an item with an error message, the resource name, and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, Webhook URL, or API Key).
- Depends on Bitrix24 API endpoints to perform operations on CRM timeline layout blocks.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Incorrect or missing Entity ID or Entity Type may lead to errors or no effect.
- Improperly formatted JSON in the Filter or Order options can cause parsing errors.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages may include authentication failures, invalid entity references, or permission denials.
Resolutions:
- Verify that the authentication method and credentials are correctly set up and have sufficient permissions.
- Ensure the Entity ID corresponds to an existing record of the specified Entity Type.
- Validate JSON syntax in the Filter and Order fields before execution.