Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 platform, specifically allowing users to retrieve information about the current authenticated user when using the "User" resource and the "Get Current User" operation. It supports multiple authentication methods including OAuth2, webhook URL, and API key.

Common scenarios for this node include:

  • Fetching details of the currently logged-in user in Bitrix24 to personalize workflows.
  • Using the current user’s data as part of a CRM automation or reporting process.
  • Integrating Bitrix24 user information into other systems or dashboards.

For example, you might use this node to get the current user's profile details and then update a record in another system based on that information.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key
Options Additional optional parameters to customize the request:
- Filter JSON object specifying filter criteria to narrow down results
- Order JSON object specifying sorting order
- Admin Mode Boolean flag indicating whether to execute the request in admin mode
- Custom Parameters JSON object for any extra parameters to be sent with the request

Output

The node outputs an array of items where each item contains a json property holding the response data from Bitrix24 about the current user. The structure of the json output corresponds to the user data fields returned by the Bitrix24 API for the current user.

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 valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
  • Relies on Bitrix24 API endpoints to fetch user data.
  • No additional external services are required beyond Bitrix24 itself.
  • Proper configuration of authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials can cause authorization failures.
    • Incorrectly formatted JSON in filter, order, or custom parameters may lead to API errors.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Errors thrown by the node will include the message from the Bitrix24 API or internal exceptions.
    • If "Continue On Fail" is enabled, errors will appear in the output JSON under the error key.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure JSON inputs are valid and correctly structured.
    • Check network access and firewall settings.
    • Enable "Continue On Fail" during testing to capture error details without stopping workflow execution.

Links and References

Discussion