When I disable the “Include n8n attribution in responses” setting in a workflow, one of the nodes fails during execution. The node works fine when attribution is enabled, but breaks consistently when attribution is turned off. This seems like unintended behavior.
Bad request - please check your parameters
Bad Request: can’t parse entities: Can’t find end of the entity starting at byte offset 210
The issue is in the Telegram Node.
What does the Text content look like, also the Parse Mode?
The text is
Thank you!
Your document has been received, and the customer has been created in Stripe.
{{ $json.name }}
Stripe Login | Sign in to the Stripe Dashboard{{ $json.id }}
Parse mode is not selected / default value
Could you please try to set it to HTML?
I think Telegram probably uses MarkdownV2 by default, which might case issue with the URL or “!” in Thank you! if it’s not escaped…
That did the trick! Much appreciated!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
