Telegram Chat Message
Triggers when a new message is posted in a Telegram chat or group. Connect your Telegram bot, then add the bot to your chat.
Trigger Communications
Triggers when a new message is posted in a Telegram chat or group. Connect your Telegram bot, then add the bot to your chat.
At a Glance
| Field | Value |
|---|---|
| Trigger ID | telegram-channel |
| Category | Communications |
| Tags | telegram, messaging, social, chat, bot, notification |
Trigger Configuration
| Field | Type | Required | Description |
|---|---|---|---|
chatId | string | Yes | Telegram chat ID of a verified DM or group. |
Trigger Result
| Field | Type | Required | Description |
|---|---|---|---|
triggeredAt | string | Yes | Timestamp when the message was received (UTC, RFC3339 format) |
platform | string | Yes | Platform identifier (always 'telegram') |
updateId | number | Yes | Telegram update ID |
messageId | number | Yes | Telegram message ID |
text | string | Yes | Message text content |
chatId | number | Yes | Telegram chat ID where the message was posted |
userId | number | Yes | Telegram user ID of the message sender |
username | string | No | Username of the message sender (without @ prefix) |
firstName | string | No | First name of the message sender |
date | number | No | Unix timestamp when the message was sent |
from | object | No | Full sender information from Telegram |
chat | object | No | Full chat information from Telegram |
entities | array | No | Message entities (mentions, hashtags, etc.) from Telegram |
Workflow Root Example
json{ "nodes": { "root": { "type": "telegram-channel", "payload": { "chatId": "-1001234567890" }, "children": [ "log_event" ] }, "log_event": { "type": "log", "payload": { "message": "Triggered at {{$trigger.triggeredAt}}" }, "children": [] } }}
Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.