Telegram Node: unable to send line break or new line after updating to 1.85.4

I am not able to send line breaks and new line after updating to 1.85.4. I am sure this was working back in 1.78.0


html parse
image

Should I just roll back?

  • n8n version: 1.85.4
  • **Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS: main Self host
  • Running n8n via Docker- Coolify
  • Operating system: Ubuntu 24.04.1 LTS

i dont want to roll back though. i love the personal folders :confused:

i added an issue in github #14428

hello @bigfather
\n won’t work in html mode… It’s not an HTML syntax. Use <br> instead

@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

Ah, yeah, seems like a small bug (or maybe an intended behavior). You can manually place newlines within the Expression mode.

Also, it works too when text passed from previous nodes with newlines.

2 Likes

@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.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.