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 user information within Bitrix24. It supports multiple authentication methods (OAuth2, webhook, API key) and provides flexibility in specifying which user to update and what data to modify.
Typical use cases include:
- Automating updates to user profiles in Bitrix24 based on external triggers or workflows.
- Synchronizing user data from other systems into Bitrix24.
- Managing user attributes programmatically without manual intervention.
For example, you might use this node to update a user's contact details or role after they complete a form on your website, ensuring your Bitrix24 user records stay current.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| User ID | The unique identifier of the user to update. |
| User Data | JSON object containing the user fields and values to update. |
| Options | Additional optional parameters: - Filter: JSON filter criteria - Order: JSON sort criteria - Admin Mode: Boolean to enable admin privileges - Custom Parameters: Additional JSON parameters |
Output
The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to update the user. This typically includes confirmation of the update or details of the updated user record.
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.
Dependencies
- Requires connection to Bitrix24 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 Bitrix24 API endpoints to perform user updates.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Incorrect User ID may result in errors or no changes applied.
- Malformed JSON in "User Data" or "Options" can lead to request failures.
- Insufficient permissions if not using admin mode when required.
Error Messages:
- Errors returned by Bitrix24 API are passed through; typical messages include authentication errors, invalid parameters, or permission denials.
- If "Continue On Fail" is disabled, the node execution will stop on error.
- To resolve, verify credentials, ensure User ID exists, validate JSON inputs, and check user permissions.