Forward telegram messages from private to public channel without "forwarded from" notice using telegram API

Questions
, ,
1

I want to forward messages from a private Telegram channel to a public Telegram channel using n8n without showing the “Forwarded from” notice. The goal is to preserve the content (text, photos, videos, etc.) while making the messages appear as if they were posted directly by the bot in the public channel.

I’ve tried multiple approaches, but I keep running into issues with Telegram API errors, despite confirming that the messages exist and are visible in the output of the previous node in n8n.

Additional Context

Here’s a summary of what I’ve tried:

1. Using TelePilot Node in n8n:
I successfully forwarded a message using the TelePilot Forward Message node. However, this included the “Forwarded from” notice, which doesn’t meet my requirements.

2. Using Telegram Bot API (forwardMessage and copyMessage):
I’ve configured an HTTP Request node to call copyMessage.
The copyMessage API, which should copy the message without showing the origin, returned an error “Bad Request: message to copy not found”

Message Existence:

The messages exist and are visible in the output of the previous node in n8n.
The “message to copy not found” error only occurs when I attempt to forward or copy the message using Telegram APIs and not when using the telepilot forward node.

Permissions:

The bot is an admin in both the private and public channels, with full permissions.

I would greatly appreciate help resolving these errors or suggestions for an alternative approach to achieve my goal. Thank you! :blush:

What is the error message (if any)?

From HTTP Request

Error code

`400`

{
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: message to copy not found"
}

Other info

Item Index

`0`

Node type

`n8n-nodes-base.httpRequest`

Node version

`1 (Latest version: 4.2)`

n8n version

`1.72.1 (Self Hosted)`

Time

`12/20/2024, 2:18:48 PM`

Stack trace


NodeApiError: Bad request - please check your parameters
    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V1/HttpRequestV1.node.js:854:27)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:741:19)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:724:51
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1155:20

Workflow JSON using telepilot and telegram API calls

Information on your n8n setup

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