Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with the Bitrix24 CRM platform, specifically focusing on the "Timeline" resource and the "Get Log Messages" operation. It retrieves log messages associated with a specified CRM entity such as a Lead, Deal, Contact, or Company. This is useful for tracking historical activities, changes, or communications related to a particular entity within Bitrix24.

Common scenarios include:

  • Auditing changes or events related to a deal or lead.
  • Displaying timeline logs in dashboards or reports.
  • Automating workflows based on specific log entries or activity types.

For example, you might use this node to fetch all log messages for a deal to analyze customer interactions or to trigger follow-up actions when certain log messages appear.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
Entity Type The type of CRM entity to retrieve log messages for. Options: Lead, Deal, Contact, Company.
Entity ID The unique identifier of the entity whose log messages are being fetched.
Options Additional parameters to customize the request:
  Filter JSON object specifying filter criteria to narrow down log messages.
  Order JSON object defining the sort order of the returned log messages.
  Start Number indicating the start position for pagination (offset).

Output

The node outputs an array of items where each item's json property contains the retrieved log messages from Bitrix24 for the specified entity. Each log message typically includes details such as timestamps, message content, author information, and other metadata relevant to the timeline entry.

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 connection to Bitrix24 CRM via one of the supported authentication methods:

    • OAuth2 authentication (recommended for production use).
    • Webhook URL authentication (simpler but less secure).
    • API key authentication.

  • Proper credentials must be configured in n8n corresponding to the chosen authentication method.

  • The node relies on Bitrix24's API endpoints to fetch timeline log messages.

Troubleshooting

  • Common Issues:

    • Incorrect or expired authentication credentials can cause authorization failures.
    • Providing an invalid or non-existent Entity ID will result in no data or errors.
    • Malformed JSON in the Filter or Order options may cause request failures.
    • Pagination parameters that exceed available data range may return empty results.

  • Error Messages:

    • Errors thrown by the Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures, invalid parameters, or network issues.

  • Resolutions:

    • Verify and update authentication credentials.
    • Ensure the Entity ID corresponds to an existing entity in Bitrix24.
    • Validate JSON syntax in filter and order fields.
    • Adjust pagination parameters appropriately.

Links and References

Discussion