Telegram Node Error: "Bad Request - Can't Parse Entities"

[Moses_Irvan]

Hi everyone,

I’m running into an issue with the Telegram node in n8n. Here’s the error I’m getting:

“Bad request - please check your parameters. Bad Request: can’t parse entities: Can’t find end of the entity starting at byte offset 1023.”

What I’ve tried so far:

• Double-checking the parameters (e.g., chat ID, message content).
• Shortening the message length to see if it’s a character limit issue.

Questions:

1. What does “can’t parse entities” mean in this context?
2. Is there a character limit or specific formatting requirement for Telegram messages in n8n?
3. How can I adjust the parameters to resolve this error?

Any advice or suggestions would be greatly appreciated!

Thanks in advance.

Information on your n8n setup

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

[Uftiman]

The error means there’s an issue with the message formatting, likely due to invalid Markdown or HTML syntax in the Telegram node. Check for unclosed tags (like * or _) or special characters (like . or -) that need escaping with a backslash (). Switch parse_mode to “MarkdownV2” or “HTML” and ensure proper formatting. If the message is long, trim it below 1024 bytes to test.

[Hugo]

I’ve run into the same issue.

We know about the error, but it’s odd that everything worked fine for a while before this started happening.

Thanks

[Hugo]

I fixed that after spending 2 hours…

1. Add Field
2. Select " Parse Mode"
3. Select HTML or Markdown2

[royamoon]

it worked. Thanks