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, specifically allowing users to update a "User Field" resource within Bitrix24. The "Update User Field" operation enables modifying custom fields associated with various entities in Bitrix24 CRM or business processes.
Common scenarios for this node include:
- Automating updates to custom user fields on CRM contacts, leads, deals, or other entities based on external triggers or workflows.
- Synchronizing data from other systems into Bitrix24 by updating user-defined fields.
- Managing dynamic field values in Bitrix24 Smart Process Automation (SPA) entities.
For example, you might use this node to update a custom "Customer Priority" field on a contact record whenever a related event occurs in another system, ensuring your CRM data stays current without manual input.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Options | Additional options for the request. Contains: - Access Token: A string token used for authentication when applicable |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after attempting to update the user field. The exact structure depends on the Bitrix24 API response but typically includes confirmation of the updated field and any relevant metadata.
If the node encounters an error during execution and is configured to continue on failure, it outputs an item with a json containing:
error: The error messageresource: The resource name ("userField")timestamp: ISO timestamp of the error occurrence
The node does not explicitly output binary data.
Dependencies
- Requires access to Bitrix24 API via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on internal helper functions to make standard Bitrix24 API calls.
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
Common Issues
- Authentication failures: Incorrect or expired tokens will cause API calls to fail. Ensure that the OAuth2 token, webhook URL, or API key is valid and has sufficient permissions.
- API rate limits: Bitrix24 may throttle requests if too many are made in a short period.
- Invalid field names or IDs: Attempting to update non-existent or incorrectly named user fields will result in errors.
- Network connectivity issues: Temporary network problems can cause request failures.
Error Messages
- Errors thrown during API calls will be surfaced as messages in the output JSON under the
errorproperty if "Continue On Fail" is enabled. - Typical error messages include authentication errors, permission denied, invalid parameters, or server errors.
- To resolve, verify credentials, check field names, and ensure the Bitrix24 account has the necessary rights.