Get File: 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
File ID file_id	string	Required	File ID

Sample request

{
  "file_id": "{{trigger.file_id}}"
}

Returns

{
  "ok": true,
  "result": {
    "file_id": "abc",
    "file_path": "photos/file_0.jpg",
    "file_size": 1024
  }
}

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

FAQ

Questions about Get File.

What does the Get File action do in Telegram?

Looks up the file path for a Telegram file ID. Combine with https://api.telegram.org/file/bot{token}/{file_path} to actually download the bytes.

What inputs does Get File require?

Required: File 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 Get File support batch operations?

Yes. Run Get File 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