Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

The Bitrix24 node enables interaction with the Bitrix24 CRM and business platform. Specifically, for the Open Lines resource with the Get Messages operation, it retrieves messages from a specified open communication session within Bitrix24's Open Lines feature. This is useful for automating workflows that involve customer support chats or other real-time communication channels managed in Bitrix24.

Typical use cases include:

  • Fetching chat messages from an ongoing or past support session to analyze conversation history.
  • Integrating chat data into external systems for reporting or follow-up actions.
  • Automating responses or triggering workflows based on message content.

Example: Automatically retrieve all messages from a specific open line session after it ends to log the conversation in a helpdesk system.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24:
- OAuth2 (recommended for production)
- Webhook (simpler but less secure)
- API Key
Session ID The unique identifier of the open line session from which to get messages (required)
Options Additional optional parameters:
- Filter: JSON object to filter messages by criteria
- Sort: JSON object to specify sorting order

Output

The node outputs an array of messages retrieved from the specified open line session. Each item in the output contains a json field representing a single message object as returned by the Bitrix24 API. The exact structure depends on the Bitrix24 Open Lines API response but typically includes message text, sender information, timestamps, and message metadata.

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.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
  • The node internally uses Bitrix24 API calls to fetch data; thus, network access to Bitrix24 endpoints is necessary.
  • No additional external dependencies beyond standard n8n credential configuration.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials will cause API call failures.
    • Incorrect or missing Session ID will result in no messages being returned or errors.
    • Malformed JSON in the Filter or Sort options may cause request errors.
  • Error messages:

    • Errors thrown by the Bitrix24 API are propagated. If "Continue On Fail" is off, execution stops with the error.
    • When "Continue On Fail" is enabled, errors are returned as part of the output JSON with fields error, resource, and timestamp.
  • Resolution tips:

    • Verify authentication credentials and renew tokens if needed.
    • Ensure the Session ID corresponds to an existing open line session.
    • Validate JSON syntax in filter and sort inputs before running the node.

Links and References

Discussion