@barn4k , as i mentioned, it was working fine in 1.78.0 and only broke in 1.85.4 . as per telegram api docs https://core.telegram.org/bots/api#html-style , \n works in html parse mode. soo, def an n8n issue. the br tag also doesnt work. it seems n8n has a different class for the content and does not recognize if there is \n in the content anymore. You can check my github issue for more details
@barn4k holy sh… you are right. this is intended and by design. i did more digging, and i actually found out the original error now for my workflow.
that the error i am getting is a character limitation. seems there is a limit of 4096 utf chars for the telegram api, and i am sending 5100… i was wondering why i am not getting my message across lol. initially i thought it was because of the \n, and it was not.
my bad. thanks. marking this as resolved. thanks man!
also, it is concluded that \n works (html parse) when using via expression, and not when manually typing the message.