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
The node integrates with the Bitrix24 platform, specifically allowing interaction with various Bitrix24 resources such as CRM entities and business processes. For the User resource with the Get Current User operation, it retrieves information about the currently authenticated user in Bitrix24.
This node is beneficial when you need to:
- Fetch details of the logged-in user for personalization or auditing.
- Use current user data to conditionally branch workflows.
- Automate tasks that depend on user identity or permissions.
Practical example:
- After authenticating via OAuth2, retrieve the current user's profile to log who initiated a workflow or to customize subsequent API calls based on user roles.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Options | Additional optional parameters: - Filter: JSON object to filter results - Order: JSON object to sort results - Admin Mode: Boolean to enable admin privileges - Custom Parameters: JSON object for extra API parameters - Access Token: String token for authentication override |
Output
The node outputs an array of items where each item contains a json property holding the response data from Bitrix24's API about the current user. The structure typically includes user details such as ID, name, email, and other profile fields provided by Bitrix24.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with:
error: Error message string.resource: The resource name ("user").timestamp: ISO timestamp of the error occurrence.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's REST API endpoints to fetch user data.
- Proper configuration of authentication credentials in n8n is necessary.
- Network access to Bitrix24 API endpoints must be available.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrectly formatted JSON in filter, order, or custom parameters causing API request failures.
- Insufficient permissions if not using admin mode when required.
Error messages:
- Authorization errors: Check that the authentication method is correctly configured and tokens are valid.
- API call failures: Verify JSON syntax in options and ensure the Bitrix24 instance is reachable.
- If "Continue On Fail" is disabled, errors will throw and stop workflow execution; enabling it allows graceful handling.