Short answer: Drop the "Telegram → New Telegram Update" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Telegram, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"raw": {"message": {"chat": {"id": 987654321,"type": "private"},"date": 1712835600,"from": {"id": 987654321,"is_bot": false,"username": "johndoe","first_name": "John"},"text": "Hello, bot!","message_id": 456},"update_id": 123456789},"text": "Hello, bot!","chat_id": 987654321,"from_id": 987654321,"chat_type": "private","from_name": "John","update_id": 123456789,"message_id": 456,"from_username": "johndoe"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| raw | object | { … } |
| raw.message | object | { … } |
| raw.message.chat | object | { … } |
| raw.message.chat.id | number | 987654321 |
| raw.message.chat.type | string | "private" |
| raw.message.date | number | 1712835600 |
| raw.message.from | object | { … } |
| raw.message.from.id | number | 987654321 |
| raw.message.from.is_bot | boolean | false |
| text | string | "Hello, bot!" |
| chat_id | number | 987654321 |
| from_id | number | 987654321 |
| chat_type | string | "private" |
| from_name | string | "John" |
| update_id | number | 123456789 |
| message_id | number | 456 |
| from_username | string | "johndoe" |
One trigger. 25+ downstream actions. Zero glue.