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 Get Layout Blocks operation, this node retrieves layout block configurations associated with a specified CRM entity (such as Lead, Deal, Contact, or Company). This is useful for workflows that need to dynamically fetch and process the UI layout blocks of timeline entries related to CRM entities.
Practical scenarios include:
- Automating retrieval of timeline layout blocks to customize or analyze how information is presented in Bitrix24.
- Integrating timeline data into external reporting or dashboard tools.
- Dynamically adjusting UI elements based on retrieved layout blocks in custom applications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Entity Type | The type of CRM entity whose timeline layout blocks are being accessed. Options: Lead, Deal, Contact, Company |
| Entity ID | The unique identifier of the specific CRM entity instance |
| Options | Additional optional parameters: - Filter: JSON object to filter results - Order: JSON object to specify sorting order - Start: Number indicating pagination start position |
Output
The node outputs an array of items where each item contains a json field representing the retrieved layout blocks data from Bitrix24 for the specified entity. The exact structure depends on Bitrix24's API response for layout blocks but generally includes details about the blocks configured on the timeline for the entity.
If binary data were involved (not indicated here), it would represent files or attachments related to timeline blocks, but this operation focuses on JSON data describing layout configuration.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs proper credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch timeline layout block data.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
- Entity not found: Verify that the provided Entity ID exists and matches the selected Entity Type.
- API rate limits or connectivity issues: Bitrix24 may throttle requests; consider adding retry logic or checking network connectivity.
- Invalid JSON in filter/order options: If using the optional JSON fields for filtering or ordering, ensure the JSON syntax is correct to avoid parsing errors.
- Empty or unexpected output: Confirm that the entity has timeline layout blocks configured; otherwise, the response may be empty.