Message to task chat
The "Message to task chat" robot writes into the task discussion by its ID in Bitrix24 (Alaio) business processes and robots. It takes a text and, optionally, Drive file IDs — the files are attached to the message. It returns a Success Y/N flag and the message ID.
The robot posts a message straight into the task discussion — participants see it in the familiar chat, while standard automation actions can only write to the notification feed, not into the task. The input is the task ID, the text, and an optional list of Drive file IDs: with files the message goes out with attachments, and files can be sent without any text. Typical use cases: tell the assignee about a priority change from a deal process; attach an invoice or a contract to the task discussion; log key process events into the task. If the task has no chat or neither text nor files are given, Success = N is returned. It returns the Y/N flag and the message ID — use them in the next steps of the business process.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Task ID | int | yes | |
| Message text | text | — | |
| Drive file IDs (optional) | string | — |
What does the robot return?
| Parameter | Type |
|---|---|
| Success (Y/N) | string |
| Message ID (0 if unknown) | int |
Scenario: an invoice file in the task discussion
- Accounting issues an invoice on a deal
- The robot posts a message with the attached invoice file into the task chat
- The assignee sees the invoice right in the discussion — no Drive digging