Reference

Reply to a message

Reply to one Telegram message (replyToMessageId = its tg_message_id from messages.list / messages.get) through the account's safety gate. Same rules as messages.send, which with replyToMessageId stays an alias.

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

Overview

Name	Value
Code	`messages.reply`
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`
In the app	Inbox → message bubble → Reply

Input fields

Field	Type	Required
`conversationId`	`uuid`	Yes
`text`	`text`	Yes
`replyToMessageId`	`integer`	Yes
`topicId`	`integer`	No
`inReplyToEventId`	`text`	No
`ifLastMessageId`	`uuid`	No
`clientMessageId`	`uuid`	No

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/messages.reply \
  -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","text":"…","replyToMessageId":1}'

Output fields (`data`)

Field	Type	Required
`timings`	`object \| null`	No
`ok`	`true`	Yes
`messageId`	`text`	Yes

Example answer

{
  "data": {
    "timings": {
      "startedAt": 1,
      "stages": {}
    },
    "ok": true,
    "messageId": "00000000-0000-4000-8000-000000000000"
  }
}

Using it over MCP

Tool messages_reply is listed on the profiles: Real-time operations (realtime), Automation setup (setup), Discover (prospecting), Reports (reports), Administration (admin), Full (full). On other profiles, find it with tools_search and run it with tools_run.

Reply to a message

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer