Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, for the Timeline resource with the Bind operation, this node binds timeline entries to specified CRM entities such as Leads, Deals, Contacts, or Companies. This is useful when you want to programmatically associate timeline events (like comments, logs, or activities) with particular CRM records to maintain a detailed history of interactions.

Common scenarios:

  • Automatically linking a new comment or log entry to a Deal after an external event.
  • Binding custom timeline data to a Contact or Lead for tracking purposes.
  • Integrating external systems that generate timeline events and associating them with CRM entities in Bitrix24.

Practical example:
You have a workflow where customer support tickets are logged outside Bitrix24. When a ticket is updated, you use this node to bind a timeline comment or log message to the corresponding Contact entity in Bitrix24, ensuring all communication history is centralized.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2, Webhook URL, or API Key.
Entity Type The type of CRM entity to bind the timeline entry to. Options: Lead, Deal, Contact, Company.
Entity ID The unique identifier of the CRM entity (Lead, Deal, Contact, or Company) to which the timeline entry will be bound.
Binding Data JSON object containing the binding details required by Bitrix24 to create the association on the timeline.
Options Additional optional parameters including:
- Filter (JSON): Criteria to filter results.
- Order (JSON): Sorting order.
- Start (number): Pagination start position.

Output

The node outputs an array of items where each item contains a json field representing the response from Bitrix24 after attempting to bind the timeline entry. The exact structure depends on the Bitrix24 API response but generally includes confirmation of the binding action or error details if it failed.

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.

This node does not output binary data.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods:

    • OAuth2 token
    • Webhook URL
    • API key

  • The node relies on Bitrix24's REST API endpoints to perform operations.

  • No additional external dependencies beyond standard n8n credential setup and network access to Bitrix24.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials leading to authorization errors.
    • Incorrect or missing Entity ID causing the bind operation to fail.
    • Malformed JSON in the Binding Data property resulting in API request errors.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
    • Typical errors include authentication failures, invalid entity references, or permission denials.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Entity ID corresponds to an existing record in Bitrix24.
    • Validate JSON syntax in Binding Data before execution.
    • Check network connectivity and firewall settings.

Links and References

Discussion