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
The "Get User" operation of the Bitrix24 node retrieves detailed information about a specific user from the Bitrix24 platform. This node is useful in scenarios where you need to fetch user data for CRM automation, reporting, or integration workflows. For example, you might use it to get user details before assigning tasks, sending notifications, or synchronizing user profiles with other systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| User ID | The unique identifier of the user to retrieve. |
| Options | Additional optional parameters: |
| - Filter | JSON object specifying filter criteria to narrow down the user query. |
| - Order | JSON object specifying sorting order of the results. |
| - Admin Mode | Boolean flag indicating whether to perform the request in admin mode. |
| - Custom Parameters | JSON object for any extra custom parameters to include in the API call. |
Output
The node outputs an array of items, each containing a json property with the user data retrieved from Bitrix24. The structure of the json output corresponds to the user fields returned by the Bitrix24 API, including standard user attributes such as ID, name, email, and any additional custom fields.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
This node does not output binary data.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Needs proper configuration of these credentials within n8n to successfully connect to the Bitrix24 API.
- Relies on Bitrix24's REST API endpoints to fetch user data.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent User ID will result in no data or errors.
- Malformed JSON in filter, order, or custom parameters may cause API request errors.
- Insufficient permissions when not using admin mode might restrict access to certain user data.
Error Messages:
- Errors returned from the Bitrix24 API are surfaced in the node output if "Continue On Fail" is enabled.
- Typical messages include authentication failures, invalid parameters, or resource not found.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check the User ID and ensure it exists in Bitrix24.
- Validate JSON syntax in optional parameters.
- Use admin mode if elevated permissions are required.