Reference
Save draft to Telegram
Keep unsent text as the chat's Telegram draft (shown on the account's other devices); empty text clears it. In a forum group pass topicId for that topic's own draft. Sends nothing.
View MarkdownThis page is generated from the source code on every release.
Keep unsent text as the chat's Telegram draft (shown on the account's other devices); empty text clears it. In a forum group pass topicId for that topic's own draft. Sends nothing.
Overview
| Name | Value |
|---|---|
| Code | conversations.save_draft |
| 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 → composer (leave a chat with text typed) |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes | |
text |
text |
Yes | |
replyToMessageId |
integer |
No | |
topicId |
integer |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/conversations.save_draft \
-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":"…"}'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: "conversations.save_draft". Tool name when listed: conversations_save_draft.