Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to update comments on timeline entries within Bitrix24. It is useful in scenarios where automated workflows need to modify existing comments programmatically, such as updating status notes, correcting information, or appending additional details to a comment in a CRM timeline.

Practical examples include:

  • Automatically updating a support ticket comment when its status changes.
  • Modifying a sales lead comment based on new data from an external system.
  • Correcting or enriching timeline comments after data validation or enrichment steps.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication.
Comment ID The unique identifier of the comment to update.
Comment Data JSON-formatted data representing the updated content and properties of the comment.
Options Additional optional parameters including:
- Filter JSON object specifying filter criteria (not typically used for update operation).
- Order JSON object specifying sort order (not typically used for update operation).
- Start Number indicating start position for pagination (not typically used for update operation).

Output

The node outputs an array containing one item per input, each with a json property holding the response from Bitrix24 after attempting to update the comment. The structure generally includes the updated comment data or an error message if the update failed.

If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with fields:

  • error: The error message string.
  • resource: The resource name ("timeline").
  • timestamp: ISO timestamp of the error occurrence.

The node does not output binary data.

Dependencies

  • Requires connection to Bitrix24 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 for the chosen authentication method.
  • Network access to Bitrix24 API endpoints is required.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials causing authorization failures.
    • Incorrect or missing Comment ID leading to "comment not found" errors.
    • Malformed JSON in the Comment Data property causing request failures.
    • Insufficient permissions in Bitrix24 account to update timeline comments.
  • Error Messages:

    • Errors returned by Bitrix24 API are passed through; typical messages include authentication errors, invalid parameters, or permission denials.
    • If "Continue On Fail" is enabled, errors are returned in the output JSON for easier debugging without stopping workflow execution.
  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Comment ID exists and is correct.
    • Validate JSON syntax in Comment Data before running the node.
    • Confirm user permissions in Bitrix24 allow comment updates.

Links and References

Discussion