Reference

Forward messages

Forward messages to another chat of the same Telegram account (counts as a send to that chat: same quota, lock and safety gate). `dropAuthor` hides the original sender.

View MarkdownThis page is generated from the source code on every release.

Forward messages to another chat of the same Telegram account (counts as a send to that chat: same quota, lock and safety gate). dropAuthor hides the original sender.

Overview

Name	Value
Code	`messages.forward`
Scope needed	`messages.send`
Risk	Write
May need confirmation	No
Runs as	Queues work for a node
Needs `Idempotency-Key`	Yes
Member roles allowed	`owner`, `manager`, `agent`
Needs a worker from version	`1.0.15`
In the app	Inbox → message menu → Forward

Input fields

Field	Type	Required
`conversationId`	`uuid`	Yes
`messageIds`	`uuid[]`	Yes
`toConversationId`	`uuid`	Yes
`dropAuthor`	`true/false`	No

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/messages.forward \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: <unique key per operation>" \
  -d '{"conversationId":"00000000-0000-0000-0000-000000000000","messageIds":[],"toConversationId":"00000000-0000-0000-0000-000000000000"}'

Output fields (`data`)

Field	Type	Required
`ok`	`true`	Yes
`jobId`	`text`	Yes

Example answer

{
  "data": {
    "ok": true,
    "jobId": "00000000-0000-4000-8000-000000000000"
  }
}

Using it over MCP

Tool messages_forward is listed on the profiles: Real-time operations (realtime). On other profiles, find it with tools_search and run it with tools_run.

Forward messages

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer