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 integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business lists. Specifically, for the Lists - Update operation, it updates an existing list in Bitrix24 by modifying its fields based on user input.
Common scenarios where this node is beneficial include:
- Automating updates to Bitrix24 lists when data changes externally.
- Synchronizing external databases or applications with Bitrix24 lists.
- Managing business process data stored in Bitrix24 lists programmatically.
For example, a user might update a project status list in Bitrix24 whenever a project milestone is reached in another system, ensuring that all stakeholders see the latest information without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| List ID | The unique identifier of the Bitrix24 list to update. |
| Fields | A collection of field name-value pairs specifying which fields to update and their new values. |
| Options | Additional optional parameters: |
| - Access Token | Override the default credential token with a specific access token string. |
| - Filter | JSON object defining filter criteria (not typically used in update but available). |
| - Order | JSON object defining sort order (not typically used in update but available). |
| - Select | Comma-separated list of fields to select (not typically used in update but available). |
Output
The node outputs an array of items corresponding to the processed resource update results. Each item contains a json property with the response from Bitrix24 after attempting to update the specified list.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error message, the resource name, and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node depends on internal helper functions to make API calls to Bitrix24.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of credentials in n8n is necessary for successful execution.
Troubleshooting
- Common issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect List ID may result in "list not found" errors.
- Improperly formatted field names or values can cause API rejections.
- Error messages:
- Errors thrown during execution will include the message from Bitrix24's API.
- If "Continue On Fail" is disabled, the node will stop execution on the first error.
- Resolutions:
- Verify and refresh authentication credentials.
- Double-check the List ID and ensure it exists in Bitrix24.
- Confirm field names match those defined in the Bitrix24 list schema.
- Use the "Fields" property carefully to avoid sending unsupported or read-only fields.