Forward Message: Telegram action

Inputs

The fields this action accepts.

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

Sample request

{
  "chat_id": "e.g. -100123456789",
  "from_chat_id": "e.g. -100987654321",
  "message_id": "e.g. 42"
}

Returns

{
  "ok": true,
  "result": {
    "message_id": 123,
    "forward_from_chat": {
      "id": -100987654321
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Forward Message.

What does the Forward Message action do in Telegram?

Forwards a message from one Telegram chat to another, preserving the original sender. Useful for mirroring an announcement to multiple groups.

What inputs does Forward Message require?

Required: Destination Chat ID, Source Chat ID, Message ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Telegram returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Forward Message support batch operations?

Yes. Run Forward Message inside a Loop node to process arrays. Tiny Command handles Telegram's rate limits automatically so you don't have to throttle manually.

More actions