Telegram Download File module troubleshooting

Hello,

This error message originates directly from Telegram.

To help us debug this issue, could you please provide more details:

• Have you verified that the file exists?
• Is the file path mapped correctly?
• Have you attempted this action again and observed the behavior?

Thank you!

I tested with images using Postman, and it functions through a two-step process.

First, I used https://api.telegram.org/bot {bot token}/getFile?fileid={fileid} to retrieve the file path.

Then, I used https://api.telegram.org/file/bot{token}/{file_path} .

I'm unsure how the Telegram Download file module is implemented or why it fails to pass the file ID correctly. The file ID is received and works with images in Postman, but it fails with voice messages across all attempts.

Have you managed to resolve your issue? I'm encountering the same error, regardless of the file type – be it videos, files, or images...

Is this a bug?

Hey, I'm interested to know if anyone has found a solution for this. I'm encountering the same message and am unable to download a voice file.

Received a response from callin.io support

Hi Maximus,

Thank you for getting in touch with us and for your interest in using our platform. Milo from the Customer Care team here.

I have inspected the scenario that you are referring to and everything looks correct on callin.io’s side. It seems like Telegram’s API is not accepting the file ID for some reason. I would suggest contacting Telegram’s team and asking them for an explanation. Please share with them the attached API request and their repsonse:

{
“response”: {
“status”: 400,
“headers”: {
“server”: “nginx/1.18.0”,
“date”: “Tue, 27 Feb 2024 16:00:06 GMT”,
“content-type”: “application/json”,
“content-length”: “111”,
“connection”: “close”,
“strict-transport-security”: “max-age=31536000; includeSubDomains; preload”,
“access-control-allow-origin”: “*”,
“access-control-expose-headers”: “Content-Length,Content-Type,Date,Server,Connection”
},
“body”: {
“ok”: false,
“errorcode”: 400,
“description”: “Bad Request: wrong fileid or the file is temporarily unavailable”
}
},
“request”: {
“url”: "<a href="" https://api.telegram.org/bot5043884045:AAGO13ulyvSj85UU2Yf2Xoy a"PuqwyMDljY/getFile" rel="noopener nofollow ugc"> https://api.telegram.org/bot5043884045:AAGO13ulyvSj85UU2Yf2Xoya PuqwyMDljY/getFile",
“qs”: {
“fileid”: “AgACAgIAAxkBAAMIZd4GQjItGSxYJuhwg9mHfUVS7eEAA9wxG1cB8UqD7EreIna1wEAAwIAA3MAAzQE”
},
“headers”: {
“user-agent”: “Make/production”,
“content-type”: “application/json”
},
“method”: “POST”
}
}

If they state that there is something wrong with our request, we can then investigate further with our dev team.

Hi there!

Thank you for sharing the insights from our support team with the community. We really appreciate it!

Please keep us updated on your progress as you connect with Telegram and receive their response.