Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, for the Timeline resource with the Add Comment operation, this node allows users to add comments to different CRM entities such as Leads, Deals, Contacts, or Companies within Bitrix24.

This functionality is useful in scenarios where automated systems need to log notes, updates, or feedback directly into the CRM timeline of a specific entity. For example, after processing a customer support ticket, an automated comment can be added to the related Deal or Contact timeline to keep all stakeholders informed.

Practical examples:

  • Automatically adding follow-up comments to a Deal timeline after a sales call.
  • Logging system-generated notes on a Lead timeline when certain criteria are met.
  • Adding internal remarks to a Contact timeline based on external triggers.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Entity Type The type of CRM entity to which the comment will be added. Options: Lead, Deal, Contact, Company.
Entity ID The unique identifier of the target entity (Lead, Deal, Contact, or Company).
Comment Data JSON-formatted data representing the comment content and any additional parameters.
Options Additional optional parameters including:
- Filter JSON filter criteria (used in other operations, not typically for Add Comment).
- Order JSON sort order (used in other operations).
- Start Pagination start position (used in other operations).

Output

The node outputs an array of items, each containing a json object representing the result of the operation. For the Add Comment operation, the output JSON typically includes confirmation details about the added comment, such as its ID or status.

If an error occurs and "Continue On Fail" is enabled, the output will contain 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 a Bitrix24 instance via one of the supported authentication methods:
    • OAuth2 authentication token (recommended for production use).
    • Bitrix24 webhook URL (simpler but less secure).
    • Bitrix24 API key.
  • Proper credentials must be configured in n8n for the chosen authentication method.
  • Network access to the Bitrix24 API endpoints.

Troubleshooting

  • Common issues:
    • Invalid or expired authentication credentials leading to authorization errors.
    • Incorrect Entity ID or Entity Type causing the API to reject the request.
    • Malformed JSON in the Comment Data property resulting in parsing errors.
  • Error messages:
    • Authorization failures: Check that the API key, OAuth2 token, or webhook URL is valid and has sufficient permissions.
    • Validation errors from Bitrix24 API: Verify that the Entity ID exists and matches the specified Entity Type.
    • JSON parse errors: Ensure the Comment Data JSON is correctly formatted.
  • Enabling "Continue On Fail" allows workflows to handle errors gracefully by capturing error details in the output.

Links and References

Discussion