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, for the Data Storage resource and the Get Entity Rights operation, it retrieves the access rights or permissions associated with a particular entity in Bitrix24.

Common scenarios where this node is beneficial include:

  • Automating permission audits by fetching current user or group rights on CRM entities.
  • Integrating Bitrix24 entity access control checks into workflows.
  • Synchronizing or reporting on entity-level permissions across systems.

For example, a workflow could use this node to get the rights of a contact record before performing an update, ensuring compliance with access policies.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key

Output

The node outputs JSON data representing the rights or permissions of the specified entity within Bitrix24. The exact structure depends on the Bitrix24 API response for entity rights but generally includes details such as which users or groups have what level of access.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object containing:

  • error: The error message.
  • resource: The resource name requested.
  • timestamp: The time when the error occurred.

No binary data output is indicated in the source code.

Dependencies

  • Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
  • Uses Bitrix24 API endpoints internally through a generic call function.
  • No additional external services beyond Bitrix24 are required.
  • Proper credentials must be configured in n8n for the chosen authentication method.

Troubleshooting

  • Common issues:

    • Incorrect or expired authentication credentials leading to authorization errors.
    • Insufficient permissions in Bitrix24 account to retrieve entity rights.
    • Network connectivity problems preventing API calls.
    • Specifying an invalid or unsupported resource or entity ID.

  • Error messages:

    • Errors thrown from the Bitrix24 API will be propagated unless "Continue On Fail" is enabled.
    • If fields or entity types cannot be loaded (in other operations), descriptive error messages are returned.

  • Resolutions:

    • Verify that the API credentials are valid and have necessary scopes/permissions.
    • Check network connectivity and Bitrix24 service status.
    • Ensure the resource and entity identifiers used are correct and exist in Bitrix24.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion