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 integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, for the Timeline resource and the Set Layout Blocks operation, this node allows users to configure the layout blocks of a timeline entry associated with a CRM entity such as a Lead, Deal, Contact, or Company.
This operation is useful when you want to customize how timeline entries appear in Bitrix24 by setting specific layout blocks programmatically. For example, you might automate updating the timeline layout for a deal after certain events or dynamically adjust the UI presentation of timeline comments or logs based on workflow logic.
Practical scenarios include:
- Customizing the timeline view for deals to highlight important information.
- Automating layout updates for contacts after data enrichment.
- Setting up consistent timeline block layouts across multiple entities via automation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key. |
| Entity Type | The type of CRM entity to which the timeline layout blocks apply. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the CRM entity instance (e.g., specific deal or contact ID). |
| Layout Blocks Data | JSON configuration defining the layout blocks to set on the timeline. |
| Options | Additional optional parameters including: |
| - Filter | JSON filter criteria to refine the scope or selection. |
| - Order | JSON specifying sort order. |
| - Start | Number indicating the start position for pagination. |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after setting the layout blocks. The exact structure depends on the Bitrix24 API response but generally confirms success or provides details about the updated layout blocks.
If an error occurs and "Continue On Fail" is enabled, 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 valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node relies on Bitrix24's REST API endpoints to perform operations.
- Proper permissions in Bitrix24 are necessary to modify timeline layout blocks.
- No additional external dependencies beyond standard n8n credential setup and network access to Bitrix24 API.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or missing Entity ID causing failures to locate the target entity.
- Malformed JSON in the Layout Blocks Data property resulting in API rejection.
- Insufficient permissions in Bitrix24 to modify timeline layouts.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical messages may include authentication failures, invalid entity references, or JSON parsing errors.
Resolutions:
- Verify and refresh authentication credentials.
- Confirm the Entity ID corresponds to an existing entity of the specified type.
- Validate JSON syntax and structure for the layout blocks configuration.
- Ensure the authenticated user has appropriate rights in Bitrix24.
Links and References
This summary is based on static analysis of the bundled source code and provided property definitions without runtime execution.