Send Document: 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
Chat ID chat_id	string	Required	Chat ID
Document URL document	string	Required	Document URL. e.g. "https://example.com/file.pdf"
Caption caption	string	Optional	Caption

Sample request

{
  "chat_id": "{{trigger.chat_id}}",
  "document": "https://example.com/file.pdf",
  "caption": "{{trigger.caption}}"
}

Returns

{
  "ok": true,
  "result": {
    "document": {
      "file_id": "abc"
    },
    "message_id": 126
  }
}

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

FAQ

Questions about Send Document.

What does the Send Document action do in Telegram?

Sends a document (any file type) to a Telegram chat by URL, with an optional caption. Telegram caps bot uploads at 50 MB per file by default.

What inputs does Send Document require?

Required: Chat ID, Document URL. 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 Send Document support batch operations?

Yes. Run Send Document 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