Telegram message

Sends messages and attachments through a bot.

Purpose

Notifies Telegram users or groups about flow results, approvals or other events. The text and recipient can be fixed or generated from table fields.

Inputs and outputs

A target with in and success/failure; the configured bot performs delivery during writing.

Parameters

Parameter	Settings and values	Options and limits
`role`	Block role: a source reads data; a target writes the result.	Default: `target`
`connection_id`	The saved connection through which the block accesses the system.	Default: `empty` Up to 64 characters
`recipient_type`	Recipient type: private, group, or auto for compatible automatic interpretation.	Options: `auto`, `private`, `group` Default: `auto`
`chats`	Chat identifiers or a template that derives the recipient from data.	Default: `empty` Up to 4000 characters
`text`	Message text; up to 4096 characters in the configuration.	Default: `empty` Up to 4096 characters
`parse_mode`	none for plain text or html for supported formatting.	Options: `none`, `html` Default: `none`
`silent`	Send without an audible notification.	Default: `disabled`
`attachments`	Attachments from File Manager, a folder or the run parameters’ “Attached file” field.	Count: 0–10
`time_zone`	The time zone for system date and time substitutions.	Default: `Europe/Kyiv` Up to 64 characters

Templates and message count

The substitution {{Назва поля}} uses the current row’s value. System tags: {{$date}}, {{$time}}, {{$datetime}}, {{$flow}}, {{$rows}}, {{$row}}, {{$table}}.

If any recipient, subject or body template contains a row field or {{$row}}, a separate message is created for every row. Otherwise, one message is created for the entire input.
{{$table}} is available only in the message body. It includes up to 1000 rows and an indication of the remainder.
All fields used in tags must exist in the input; TEMPLATE_FIELD_MISSING is detected during preparation.
Dates and times use the specified time_zone. Data values are escaped for formatted messages.

Step-by-step configuration

Create a bot connection and check access to the required recipient.
Select the recipient type and chat in the available interface, or specify a supported identifier.
Write the message and insert tags. Check how many messages will be generated.
Add attachments and silent if needed; set the time zone.
Check formatting and preparation, then start delivery.

Rules and diagnostics

The bot must be accessible to the recipient and have the required group permissions; the block itself does not grant these permissions.
Up to 10 attachment sources. Duplicate sources are prohibited.
HTML must comply with Telegram’s allowed subset; invalid/unclosed tags cause TELEGRAM_MARKUP. The editor helps create supported formatting.
A large table can create many message parts; for substantial data, an attached file or brief summary is more convenient.
After partial sending, check the log before retrying to avoid duplicates.
An empty active input does not create a message: EMPTY_STAGE. Up to 10000 messages are allowed per block per run; for more, filter or split the dataset.
Losing the response during external sending is treated as an uncertain result: the system does not automatically resend that message.
After substitutions, text is automatically divided into parts of up to 4096 characters while preserving valid HTML. An individual file is limited to 50 MB; a folder attachment adds up to 20 files.

Configuration example

For a single notification, set a fixed group chat and the text “Flow {{$flow}} completed. Processed {{$rows}} rows, {{$datetime}}”. There are no row fields here, so one summary is generated.