New Task Card: Overview of Changes
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
The new task card moved comments to the task chat. This page helps you choose the current REST methods for working with comments, files, events, results, and widgets after switching to the new card.
The changes are available starting from module version tasks 25.700.0. The old task methods continue to work, except for comment operations, which are now performed through chat methods.
When to Use This Page
Use this page if your integration:
- retrieves, updates, or deletes task comments
- sends a message or file to the task discussion
- handles comment events
- works with task results created from comments
- places widgets in the task card
If the integration only creates, updates, retrieves, or deletes tasks without working with comments, use the methods in the Tasks section.
Operating Conditions
|
Condition |
Description |
|
Module version |
New task card changes are available starting from |
|
Call format |
Old API methods are called through |
|
User permissions |
The user must have access to the task and the chat linked to it |
|
Scope for tasks |
For old task methods, use the |
|
Scope for chats and files |
For chat methods and sending files to the task chat, use the |
New Task Card Workflow
In the new card, a task has a linked chat. A task comment is stored as a message in that chat:
- Get the task chat identifier using the tasks.task.get method
- Use the chat identifier in chat methods. If the method accepts
DIALOG_ID, pass the value in thechat{CHAT_ID}format, for examplechat58 - Use tasks.task.chat.message.send to send a new message
- Use the methods from the Chats section to update, delete, and retrieve messages
Identifier Mapping
|
Identifier |
Returned Where |
What It Is Used For |
|
|
Old response format of tasks.task.get |
Task chat identifier for chat methods |
|
|
New response format of tasks.task.get through |
Task chat identifier for chat methods |
|
|
Formed from the chat identifier |
Value for chat methods that work with a dialog. For a task chat, pass |
|
|
New response format of tasks.task.get through |
Identifier of the task linked to the chat |
|
|
New response format of tasks.task.get through |
Type of the chat binding. For a task, the value is |
|
|
OnTaskCommentAdd event |
Identifier of the message in the task chat |
|
|
OnTaskCommentAdd event |
Task identifier |
|
|
tasks.task.result.list response |
Marker of a task result linked to the new card |
Migration Quick Reference
|
Operation |
Old Approach |
Status in the New Card |
New Approach |
|
Add a comment |
Works |
Existing integrations can continue using the old method. For new integrations, use tasks.task.chat.message.send |
|
|
Update a comment |
|
Does not work |
|
|
Delete a comment |
|
Does not work |
|
|
Retrieve the comment list |
|
Does not work |
Get task chat messages using im.dialog.messages.get |
|
Send a file to the task chat |
Task comment methods |
Not suitable for the new card |
|
|
Retrieve a task result |
Works |
Keep in mind that results for the new card are returned with |
|
|
Add a result from a comment |
Does not work |
Creating a result from a new-card comment is not available through the old method |
|
|
Delete a result from a comment |
Does not work |
Removing the link between a result and a new-card comment is not available through the old method |
How to Get the Task Chat Identifier
Old API Version
POST https://{installation_address}/rest/{user_id}/{rest_app_password}/tasks.task.get
{
"taskId": 51,
"select": ["CHAT_ID"]
}
Example response:
{
"result": {
"task": {
"id": "51",
"chatId": 2537,
"favorite": "N",
"group": [],
"action": {}
}
}
}
New API Version
Request the fields chat.id, chat.entityId, chat.entityType for the task:
POST https://{installation_address}/rest/api/{user_id}/{rest_app_password}/tasks.task.get
{
"id": 51,
"select": ["id", "chat.id", "chat.entityId", "chat.entityType"]
}
Example response:
{
"result": {
"item": {
"id": 51,
"chat": {
"id": 58,
"entityId": 51,
"entityType": "TASKS_TASK"
}
}
}
}
Starting from module version tasks 25.700.0, some methods can be called in the new format.
The new API call differs by the addition of the /api/ segment in the request.
Old version:
https://{installation_address}/rest/{user_id}/{rest_app_password}/tasks.task.get
New version:
https://{installation_address}/rest/api/{user_id}/{rest_app_password}/tasks.task.get
Documentation for the new version of the method call is available in OpenAPI format. To get the OpenAPI description, call the documentation method:
https://{installation_address}/rest/api/{user_id}/{rest_app_password}/documentation
Events
-
The event OnTaskCommentAdd works. When working with the new task card, the handler will receive parameters:
MESSAGE_IDwith the identifier of the message in the task chatTASK_IDwith the identifier of the task'ID' => 0, the comment identifier will be equal to zero
-
The events OnTaskCommentUpdate and OnTaskCommentDelete do not work in the new task card.
Task Result
-
The method tasks.task.result.list works. When working with the new task card, all task results will be returned with the parameter
commentId: 0. -
The methods tasks.task.result.addFromComment and tasks.task.result.deleteFromComment do not work in the new task card.
Widgets
The locations of the widgets TASK_VIEW_SIDEBAR, TASK_VIEW_TOP_PANEL, TASK_VIEW_TAB are no longer relevant in the new task card. In the new card, all widgets are displayed in a single "Applications" block.
All previously registered widgets continue to work. New widgets can also be registered, and they will be displayed in the "Applications" block.
