Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various Bitrix24 resources. Specifically, the "Data Storage" resource with the "Get Entity" operation enables retrieving detailed information about a specific entity by its ID.

Common scenarios for this node include:

  • Fetching CRM records such as contacts, deals, or leads by their unique identifiers.
  • Integrating Bitrix24 data retrieval into automated workflows, e.g., pulling customer details before processing orders.
  • Synchronizing Bitrix24 entities with other systems by extracting entity data on demand.

Practical example:

  • A workflow that triggers when a new order is created in an external system and uses this node to fetch the corresponding contact's full details from Bitrix24 by specifying the entity ID.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication.
Entity ID The unique identifier of the entity to retrieve from Bitrix24. This is a required string input.

Output

The node outputs JSON data representing the retrieved entity's details from Bitrix24. The structure of the JSON depends on the entity type but generally includes all fields associated with that entity, such as IDs, names, dates, and custom fields.

If the node supports binary data output (not explicitly shown in the provided code), it would typically represent files or attachments related to the entity, but this is not indicated here.

Dependencies

  • Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
  • Relies on Bitrix24's REST API endpoints to fetch entity data.
  • The node expects proper configuration of these credentials within n8n to successfully connect and authenticate.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials leading to authorization errors.
    • Incorrect or non-existent Entity ID causing "entity not found" errors.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • Errors thrown during execution will include the error message from Bitrix24 API or internal exceptions.
    • If continueOnFail is enabled, errors are returned as part of the output JSON with fields error, resource, and timestamp.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Confirm the Entity ID exists and is correctly formatted.
    • Check network access and firewall settings.
    • Enable continueOnFail cautiously to handle errors gracefully in workflows.

Links and References

Discussion