hm, can see how that can be needed (esp. for you) but honestly do not want to add features for every edge case and so make things unnecessarily more complicated/confusing for all others (at least not if I can avoid it somehow). So I wonder if it would not be better and easier if you would simply add an entry to your /etc/hosts file. With an entry there you can tell your host to resolve api.telegram.org to whatever you want it to. It should be very simple to do and would not require any code changes at all.
Sorry, do not understand. The Telegram-API officially supports proxy-servers? Can not understand right how that would work for a REST-API. Maybe you mean some kind of SDK they offer support that?
Yes, I need help here.
As I understand it, you offer the following solution
Change /etc/hosts/ and put another host there for the telegram api.
Next, I will need to accept the request on another hosting and redirect it to the telegram api. Right?
Ah ok. But I still do not totally understand the issue. Where are you running n8n? Locally or on a server? Can you not just run n8n on that inexpensive server? There are so many cheap ones out there where telegram is for sure not blocked and then there would be no need for a proxy.