Short answer: You can forward message in Telegram by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Telegram Forward Message action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Destination Chat ID chat_id | string | Required | Destination Chat ID. Example: -100123456789 |
Source Chat ID from_chat_id | string | Required | Source Chat ID. Example: -100987654321 |
Message ID message_id | string | Required | Message ID. Example: 42 |
{"chat_id": "e.g. -100123456789","from_chat_id": "e.g. -100987654321","message_id": "e.g. 42"}
{"ok": true,"result": {"message_id": 123,"forward_from_chat": {"id": -100987654321}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.