Send Media Group
telegram.send_media_group
ActionChat & messagingconnection required
Calls the Telegram API with the connection's credentials.
Send 2-10 photos, videos, documents or audio files as one album.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Telegram
- Secret shape
- the bot token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
chat_id The chat to send to: a numeric chat/user id, or an @channelusername. | string | Yes | — | — | — |
media JSON array of InputMedia objects, e.g. {"type": "photo", "media": "<file_id or https URL>", "caption": "…"}. Telegram requires 2-10 items and rejects an album with fewer. | array | Yes | — | 2–10 characters; array of object | [{"media":"<file_id or https URL>","type":"photo"},{"caption":"second","media":"<file_id or https URL>","type":"photo"}] |
disable_notification Deliver silently — the recipient's device stays quiet. | boolean | No | — | — | — |
protect_content Stop recipients forwarding or saving the album. | boolean | No | — | — | — |
message_thread_id Topic id inside a forum supergroup; leave blank for the main thread. | integer | No | — | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"media": [
{
"media": "<file_id or https URL>",
"type": "photo"
},
{
"caption": "second",
"media": "<file_id or https URL>",
"type": "photo"
}
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Telegram accepted the call. | boolean | true |
chat_id Chat the album landed in. | string | — |
message_ids Id of each message in the album. | array | — |
messages The full Message object for each item. | array | — |
count How many messages the album became. | number | — |
{
"chat_id": "",
"count": 0,
"message_ids": [],
"messages": [],
"ok": true
}Notes
- chat_id is a numeric chat/user id or an @channelusername. A bot can only message a user who started it, or a group/channel it has been added to.
- The bot token sits in the request URL, so it is redacted out of every error message and dry-run report these nodes produce.
- Telegram answers HTTP 200 even for failures; the node reads the {'ok': …} envelope and raises on ok:false with Telegram's own description.
- Documents and audio files can only be grouped with items of the same type; photos and videos may be mixed.
- sendMediaGroup takes no reply_markup — an album cannot carry a keyboard.
See Send Media Group run in a workflow.
In a technical demo we add the Telegram connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.