Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The "Update Chat" operation in this Bitrix24 node allows users to modify properties of an existing chat within the Bitrix24 platform. This includes changing the chat's title, description, and color. It is useful for scenarios where chat metadata needs to be updated dynamically, such as renaming a project discussion group, updating chat context, or visually categorizing chats by color.

Practical examples:

  • Renaming a team chat after a project milestone.
  • Adding or updating a description to clarify the chat’s purpose.
  • Changing the chat color to reflect priority or status.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook, or API Key.
Chat ID The unique identifier of the chat to update.
Chat Title The new title for the chat (required).
Update Fields Collection of fields to update on the chat:
- Title New chat title (string).
- Description New chat description (string).
- Color New chat color. Options: Red, Green, Blue, Yellow, Pink, Purple, Orange, Gray.

Output

The node outputs JSON data representing the result of the update operation. Typically, this will include confirmation details about the updated chat, such as its ID and the new property values. If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message, resource name, and timestamp.

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 the Bitrix24 API endpoint.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials causing authorization failures.
    • Incorrect or missing Chat ID leading to "chat not found" errors.
    • Insufficient permissions to update chat properties.
    • Providing empty or invalid values for required fields like Chat Title.

  • Error messages:

    • Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
    • Typical error messages may include authentication failures, invalid parameters, or permission denials.

  • Resolutions:

    • Verify that the authentication credentials are valid and have necessary scopes/permissions.
    • Double-check the Chat ID is correct and corresponds to an existing chat.
    • Ensure required fields are provided and valid.
    • Enable "Continue On Fail" to capture error details for debugging.

Links and References

Discussion