Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The node integrates with the Bitrix24 platform, enabling interaction with various Bitrix24 resources including CRM entities and business processes. Specifically, for the Open Lines resource with the Get Open Lines operation, it retrieves information about open communication lines configured in Bitrix24. This is useful for scenarios where you want to monitor or manage customer communication channels such as chats, calls, or social media integrations within Bitrix24.

Practical examples include:

  • Fetching a list of all active open lines to display their status or details in an external dashboard.
  • Automating workflows based on the availability or configuration of open lines.
  • Integrating open line data into other systems for unified customer support management.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication.
Options Additional parameters to customize the request:
  Filter JSON object specifying filter criteria to narrow down which open lines to retrieve.
  Sort JSON object defining the sort order of the returned open lines.

Output

The node outputs an array of items where each item's json property contains the data retrieved from Bitrix24 about open lines. The structure corresponds to the Bitrix24 API response for open lines, typically including fields such as IDs, names, statuses, and configuration details of each open line.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs an item with an error field describing the issue, along with the resource name and a timestamp.

No binary data output is involved in this operation.

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 open line data.
  • No additional external services are required beyond Bitrix24 itself.
  • Proper configuration of credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or expired credentials.
    • Incorrectly formatted JSON in the Filter or Sort options causing API errors.
    • Network connectivity issues preventing access to Bitrix24 API.

  • Error Messages:

    • Errors thrown by the node will include the message from the Bitrix24 API or internal processing errors.
    • If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an error field.

  • Resolutions:

    • Verify that the selected authentication method is correctly set up and credentials are valid.
    • Ensure JSON syntax in Filter and Sort fields is correct.
    • Check network connectivity and Bitrix24 service status.
    • Review Bitrix24 API permissions to confirm the authenticated user has access to open lines data.

Links and References

Discussion