Telegram trigger downloads the lowest image size if the selected size isn't available

Questions
1

Describe the problem/error/question

When using the Telegram trigger, enabling Download Images/Files, and setting Image Size to Extra Large results in downloading the smallest (~90x90 pixels) image size in case the largest size isn’t provided by Telegram.
This can happen when an image is shared that is smaller in resolution than the selected image size.

To Reproduce

  1. Create a Telegram trigger node

  2. Add & enable Download Images/Files

  3. Add & set Image Size to Extra Large

  4. Share an 500x500 image on Telegram with the trigger chat

  5. Observe that the Telegram trigger node outputs the 90x90 resolution variant

If the node is configured to output the biggest image size, it shouldn’t output the smallest image size instead.

480411745-4d5dce66-5275-415e-bbd0-0b01b547da3d
480411745-4d5dce66-5275-415e-bbd0-0b01b547da3d514×562 26.6 KB

480411744-986f927e-a7e8-4e2c-aa44-0d032a17a164
480411744-986f927e-a7e8-4e2c-aa44-0d032a17a164436×1081 65.2 KB

Also reported as a bug at Telegram trigger downloads the lowest image size if the selected size isn't available · Issue #18625 · n8n-io/n8n · GitHub , but got flagged as a feature or enhancement request.

Since it’s not quite a request for a new feature, I’m posting it here instead of in the feature request category.

Of course, this can be worked around by disabling Download Images/Files and handling it manually.

What is the error message (if any)?

There’s no error message in this case.

Please share your workflow

Share the output returned by the last node

(personal details removed)

[
  {
    "update_id": 123,
    "message": {
      "message_id": 123,
      "from": {
        "id": 123,
        "is_bot": false,
        "first_name": "XX",
        "username": "XX",
        "language_code": "en"
      },
      "chat": {
        "id": 123,
        "first_name": "XX",
        "username": "XX",
        "type": "private"
      },
      "date": 1755765887,
      "photo": [
        {
          "file_id": "XX",
          "file_unique_id": "XX",
          "file_size": 337,
          "width": 90,
          "height": 90
        },
        {
          "file_id": "XX",
          "file_unique_id": "XX",
          "file_size": 884,
          "width": 320,
          "height": 320
        },
        {
          "file_id": "XX",
          "file_unique_id": "XX",
          "file_size": 1102,
          "width": 500,
          "height": 500
        }
      ]
    }
  }
]

Information on your n8n setup

  • n8n version: 1.107.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 24.04
2

@Ziyan ok so you mean you are posting this as a request and not a question.

3

@Zelite I checked the two categories, and in the questions category, similar issues seemed to be reported, so I thought it’s an appropriate place to post. Also, the post template starts with “Describe the problem/error/question” - which I also thought fits my post. In the feature requests category, people seem to be posting explicit new feature and node requests, rather than problems they encountered like I do.

However, feel free to move it, or just delete it if it’s inappropriate to post it here. I just wanted the team to be aware of this, just in case… I’m not posting it as a critical/important request, and provided a workaround until then.

4

No problem at all my friend. I only asked to know how I could help you.

It’s good to know mate, keep it up.

The team will respond to your post soon.

1 Like