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, a CRM and business platform, to perform various operations on its resources. Specifically, the "Lists" resource with the "Get" operation allows users to retrieve data from a specified list within Bitrix24. This is useful for workflows that need to fetch list data such as contacts, deals, or custom lists stored in Bitrix24.
Common scenarios include:
- Fetching a list of items (e.g., contacts or deals) to process or analyze them further.
- Retrieving filtered or sorted list data based on specific criteria.
- Selecting only certain fields from the list to optimize data handling.
Example: A user wants to get all entries from a particular Bitrix24 list filtered by status and sorted by creation date, then use this data in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| List ID | The unique identifier of the Bitrix24 list to retrieve data from. |
| Options | Additional optional parameters: |
| - Access Token | Use a specific access token instead of the one from credentials. |
| - Filter | JSON object defining filter criteria to narrow down the list items returned. |
| - Order | JSON object specifying the sort order of the results. |
| - Select | Comma-separated string listing which fields to include in the output. |
Output
The node outputs an array of items where each item contains a json object representing a single entry from the specified Bitrix24 list. The structure of each json object corresponds to the fields selected or returned by default from the list.
If binary data were involved (not indicated here), it would be included in a separate binary property, but this node focuses on JSON data retrieval.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs proper configuration of credentials in n8n for the chosen authentication method.
- Uses Bitrix24 API endpoints internally to fetch list data.
Troubleshooting
- Authentication errors: Ensure the correct authentication method is selected and credentials are valid. For OAuth2, tokens must not be expired.
- Invalid List ID: If the List ID does not exist or is incorrect, the API call will fail. Verify the List ID in Bitrix24.
- Malformed JSON in Filter or Order: The filter and order options expect valid JSON strings. Invalid JSON will cause errors.
- Access token override issues: If providing an access token manually, ensure it has sufficient permissions and is current.
- API rate limits or connectivity issues: Network problems or Bitrix24 API limits may cause failures; retry or check API usage.
Error messages typically include the API error message returned by Bitrix24, which can guide resolution.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Lists API Reference
- n8n Documentation on Bitrix24 Node (for general usage guidance)