Reference

Schedule a message (kept by Telegram)

Schedule a text message with Telegram itself: Telegram sends it at `at` (10 seconds to 365 days ahead) even if the machine is off. Counted in limits now; appears in the chat when it goes out.

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

Schedule a text message with Telegram itself: Telegram sends it at at (10 seconds to 365 days ahead) even if the machine is off. Counted in limits now; appears in the chat when it goes out.

Overview

Name	Value
Code	`messages.schedule`
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.19`
In the app	Inbox → right-click Send → Schedule message

Input fields

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

Example request

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

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

Not listed on any profile: call tools_describe then tools_run with code: "messages.schedule". Tool name when listed: messages_schedule.

Schedule a message (kept by Telegram)

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer