Bitrix24Install

Overview

This node integrates with the Bitrix24 platform, allowing users to interact with various Bitrix24 resources and operations. Specifically, for the Open Lines resource and the Get Session operation, it retrieves session information related to Bitrix24's Open Lines feature, which is typically used for managing customer communication channels such as chats or messaging sessions.

Common scenarios where this node is beneficial include:

• Fetching details about active or past chat sessions in Bitrix24 Open Lines.
• Automating workflows that depend on session data from customer interactions.
• Integrating Bitrix24 Open Lines session data into other systems or dashboards.

For example, a user might use this node to get session details after a chat ends to trigger follow-up actions or analytics.

Properties

Output

The node outputs an array of items where each item's json property contains the session data retrieved from Bitrix24 Open Lines. The exact structure depends on the Bitrix24 API response for the "Get Session" operation but generally includes session identifiers, timestamps, participant info, and status.

If the node encounters an error 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.

The node does not output binary data.

Dependencies

• Requires access to a Bitrix24 account with appropriate permissions.
• Needs one of the following authentication credentials configured in n8n:
  • An OAuth2 credential for Bitrix24.
  • A Bitrix24 webhook URL.
  • An API key credential for Bitrix24.
• Uses internal helper functions to make standard API calls to Bitrix24.

Troubleshooting

• Common issues:

  • Incorrect or expired authentication credentials will cause authentication failures.
  • Improperly formatted JSON in the Filter or Sort options may cause API errors.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • Errors thrown by the Bitrix24 API are passed through; these often indicate invalid parameters or permission issues.
  • If the node fails and "Continue On Fail" is enabled, the error message is included in the output JSON under the error key.

• Resolutions:

  • Verify and refresh authentication credentials.
  • Ensure JSON inputs for filtering and sorting are valid.
  • Check network connectivity and Bitrix24 service status.

Links and References

• Bitrix24 Open Lines API Documentation
• Bitrix24 Developer Documentation
• n8n Documentation on Credentials