When I turn off the n8n attribution, my Telegram node throws an error. It works fine if I leave it on. The only thing I can think of is that it’s because my account is on trial. Has anyone else run into this or can confirm if it’s trial-related?
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Could you please post the actual error message/details? Does the message indicate that something isn’t allowed (license issue), or does the error seem more like something that wasn’t handled correctly (unintended)?
same problem - if set OFF - take the errore
if set ON - all works
- n8n version: LAST
- Database (default: SQLite): DEFAULT
- n8n EXECUTIONS_PROCESS setting (default: own, main): just default cloud settings
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
- Operating system: WIN_10
From Telegram
Error code
400
Full message
{ "ok": false, "error_code": 400, "description": "Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 18" }
Other info
Node type
n8n-nodes-base.telegram
Node version
1.2 (Latest)
n8n version
1.81.4 (Cloud)
Time
3/5/2025, 12:28:11 PM
Stack trace
NodeApiError: Bad request - please check your parameters at ExecuteContext.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/GenericFunctions.js:118:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/Telegram.node.js:1795:36) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:660:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:891:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1224:20
Telegram
Test step
Parameters
Settings
Credential to connect with
Resource
Operation
Chat ID
Fixed
Expression
Text
Fixed
Expression
{{ $(‘Limit’).item.json.link }}
Reply Markup
Fixed
Expression
Additional Fields
Append n8n Attribution
Fixed
Expression
I wish this node would…
Problem in node ‘Telegram‘
Bad request - please check your parameters
Hey, I just tried replicating this on 1.82.1, but couldn’t. For me, the send message
operation worked the same with or without n8n attribution. And this is definitely not something related to trial or non-trial users.
Basic workflow example (can you maybe share yours or a simple example to try to debug?)
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.