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 allows interaction with the Bitrix24 CRM and business platform. Specifically, the "Lists" resource with the "Get Elements" operation enables users to retrieve elements (items) from a specified list within Bitrix24.
This node is beneficial in scenarios where you want to automate workflows involving data stored in Bitrix24 lists, such as syncing list items with other systems, generating reports based on list data, or triggering actions based on list content.
For example, you could use this node to fetch all tasks or records from a particular list to process them further in an automation workflow, or to filter and sort list elements dynamically based on certain criteria.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| List ID | The identifier of the Bitrix24 list from which to retrieve elements. |
| Options | Additional optional parameters: |
| - Access Token | Use a specific access token instead of the one from credentials. |
| - Filter | JSON-formatted filter criteria to narrow down the elements retrieved. |
| - Order | JSON-formatted sorting order for the results. |
| - Select | Comma-separated list of fields to select from each element. |
Output
The node outputs an array of elements retrieved from the specified Bitrix24 list. Each element is represented as a JSON object containing the fields requested (or all fields if none specified).
If binary data is involved (not explicitly shown in this operation), it would represent files or attachments related to list elements.
In case of errors and if the node is configured to continue on failure, the output will contain an error object with the error message, resource name, and timestamp.
Dependencies
- Requires valid authentication to Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node depends on Bitrix24's API endpoints to fetch list elements.
- Proper configuration of credentials in n8n is necessary to authenticate requests.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect List ID may result in empty responses or errors.
- Malformed JSON in filter or order options can cause request failures.
Error Messages:
- Errors returned by the Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical errors include authentication failures, invalid parameters, or network issues.
Resolutions:
- Verify that the authentication credentials are correct and have not expired.
- Double-check the List ID and ensure it exists in your Bitrix24 account.
- Validate JSON syntax in filter and order fields before running the node.