Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
This node integrates with the Bitrix24 platform, specifically allowing users to interact with various Bitrix24 resources such as CRM entities and business platform features. The "Get User" operation under the "User" resource retrieves detailed information about a specific user in Bitrix24 by their user ID.
Common scenarios for this node include:
- Fetching user details for automation workflows that require user data.
- Integrating Bitrix24 user information into other systems or reports.
- Validating or enriching data based on Bitrix24 user profiles.
For example, you might use this node to get the profile of a sales representative before assigning a deal or to retrieve contact details for notifications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook, 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 results. |
| - Order | JSON object specifying sorting order of results. |
| - Admin Mode | Boolean flag indicating whether to perform the operation in admin mode (with elevated privileges). |
| - Custom Parameters | JSON object for any extra parameters to pass to the API call. |
| - Access Token | String token for authentication if needed explicitly. |
Output
The node outputs an array of items where each item contains a json field with the user data retrieved from Bitrix24. The structure of the json output corresponds directly to the user object returned by the Bitrix24 API, including fields such as user ID, name, email, roles, and other profile details.
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.
The node does not output binary data.
Dependencies
- Requires access to the Bitrix24 API via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network connectivity to Bitrix24 endpoints is necessary.
- No additional external libraries beyond those bundled are required.
Troubleshooting
Common Issues:
- Invalid or missing user ID parameter will cause the API call to fail.
- Incorrect or expired authentication credentials can lead to authorization errors.
- Using webhook authentication may have limited permissions compared to OAuth2.
- Improperly formatted JSON in filter, order, or custom parameters can cause request failures.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node's error output if "continue on fail" is enabled.
- Typical errors include "Unauthorized", "User not found", or "Invalid parameters".
Resolutions:
- Verify the user ID exists and is correct.
- Ensure credentials are valid and have sufficient permissions.
- Validate JSON syntax in optional parameters.
- Prefer OAuth2 authentication for production environments due to better security and capabilities.