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 Bitrix24, a CRM and business platform, to perform various operations on its resources. Specifically, the "Lists" resource with the "Update Field" operation allows users to update a field within a specified list in Bitrix24. This is useful for managing custom lists by modifying their fields' properties or values dynamically.
Common scenarios include:
- Updating metadata or configuration of a list field.
- Changing field names or values programmatically based on workflow logic.
- Automating list maintenance tasks without manual intervention.
For example, you might use this node to rename a field in a project management list or update a status field's value in a customer feedback list.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| List ID | The identifier of the list where the field exists and will be updated. |
| Field ID | The identifier of the specific field within the list to update. |
| Fields | Collection of fields to set/update, each with: |
| - Field Name: The name of the field property to update. | |
| - Field Value: The new value to assign to that field property. | |
| Options | Additional optional parameters: |
| - Access Token | Override the default access token with a specific one. |
| - Filter | JSON object specifying filter criteria (not typically used for update field but available). |
| - Order | JSON object specifying sort order (not typically used for update field but available). |
| - Select | Comma-separated list of fields to select (not typically used for update field but available). |
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after attempting to update the field. The exact structure depends on the Bitrix24 API response but generally includes confirmation of the update or error details.
If the operation fails and "Continue On Fail" is enabled, the output item will contain an error field with the error message, the resource name, and a timestamp.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Needs appropriate permissions in Bitrix24 to update list fields.
- No additional external dependencies beyond Bitrix24 API access.
- Configuration of credentials in n8n is necessary depending on chosen authentication.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured and tokens/keys are valid.
- Invalid List ID or Field ID: Verify that the provided IDs exist in Bitrix24 and are correct.
- Permission denied: The authenticated user must have rights to modify the list and its fields.
- Malformed Fields input: The "Fields" collection must be properly structured with valid field names and values.
- API rate limits or connectivity issues: Check network connectivity and Bitrix24 API usage limits.
Common error messages will include descriptive text from Bitrix24 API responses. Enabling "Continue On Fail" can help workflows handle errors gracefully.