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 Bitrix24's Lists resource to retrieve a specific element from a list. It is useful when you need to fetch detailed information about a particular item stored in a Bitrix24 list, such as retrieving customer data, task details, or any custom list entries.
Practical examples include:
- Fetching a contact or lead record by its element ID.
- Retrieving a specific task or project detail from a list.
- Accessing custom business data stored in Bitrix24 lists for further processing or automation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| List ID | The unique identifier of the Bitrix24 list from which to get the element. |
| Element ID | The unique identifier of the element within the list to retrieve. |
| 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 search (not typically used for single element retrieval). |
| - Order | JSON-formatted sort order for results (not typically relevant for single element retrieval). |
| - Select | Comma-separated list of fields to select and return for the element. |
Output
The node outputs a JSON object representing the retrieved element from the specified Bitrix24 list. This JSON contains all the fields of the element as returned by the Bitrix24 API, including standard and custom fields.
If binary data is involved (not typical for this operation), it would represent files or attachments related to the element, but this operation primarily returns structured JSON data.
Dependencies
- Requires an active Bitrix24 account with API access.
- Requires authentication via one of the supported methods: OAuth2, webhook URL, or API key.
- The node depends on Bitrix24 API endpoints for lists and elements.
- Proper permissions must be granted to the API credentials to read list elements.
Troubleshooting
Common issues:
- Invalid or missing List ID or Element ID will cause errors.
- Insufficient permissions or incorrect authentication method can result in authorization errors.
- Network connectivity issues may prevent API calls.
- Using an expired or invalid access token will cause authentication failures.
Error messages:
- Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical error messages include "Element not found," "Invalid authentication," or "Access denied."
Resolutions:
- Verify that List ID and Element ID are correct and exist in Bitrix24.
- Ensure the selected authentication method is properly configured and valid.
- Refresh or regenerate access tokens if expired.
- Check network connectivity and firewall settings.