Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically allowing users to add comments to tasks within Bitrix24. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security and deployment scenarios.

A common use case is automating task collaboration by programmatically adding comments to tasks based on external triggers or workflows. For example, when a customer support ticket is updated in another system, this node can add a comment to the corresponding Bitrix24 task to keep all team members informed.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key.
Task ID The unique identifier of the task to which the comment will be added.
Comment Text The text content of the comment to add to the specified task.
Options Additional optional parameters as JSON objects: Filter, Order, Select, Group, Custom Parameters.
  • Options fields allow advanced customization of the request but are not mandatory for adding a comment.

Output

The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after adding the comment. This typically includes confirmation details about the created comment.

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 access to a Bitrix24 account with appropriate permissions to add comments to tasks.
  • Needs one of the following authentication credentials configured in n8n:
    • OAuth2 token credential
    • Webhook URL credential
    • API key credential
  • Uses Bitrix24 REST API endpoints internally to perform operations.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication credentials will cause authorization failures.
    • Incorrect Task ID may result in errors indicating the task was not found.
    • Malformed JSON in the "Options" property can cause request failures.

  • Error Messages:

    • Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical messages include authentication errors, permission denied, or invalid parameters.

  • Resolution Tips:

    • Verify that the authentication method and credentials are correctly set up and valid.
    • Confirm the Task ID exists and is accessible by the authenticated user.
    • Ensure any JSON input in options is well-formed and matches expected schema.

Links and References

Discussion