Send Telegram message or document

The conversation's peer id, as returned by get_inbox (e.g. "8591421602" for Saved Messages; negative ids are channels and groups). Confirm the target with the user before sending — a peer id is not human-readable, so echo back the chatTitle this returns.

The message text. Required on its own for a text message; sent as the document's caption when a file is also given. Omit for a document with no caption.

Required with fileBase64: the name Telegram gives the document, including its extension (e.g. "report.pdf"). Also what the script verifies the sent bubble against. Not used with the `attachment` input, which is sent under its own name.

A file to send as a document, bound through the platform's own file channel. Preferred over fileBase64: it carries the bytes outside the argument payload, so it is not limited by the request size. Telegram has no file input of its own, so the file is landed on a throwaway input the script creates and then handed to Telegram's paste handler — which means it is sent under the name 'attachment'. Use fileBase64 when the stored filename matters.

Optional: base64 of a file's bytes, to send it as a document. Requires filename. Prefer the `attachment` input, which has no payload ceiling. Keep this modest (a few MB); the base64 travels inside the request.

Optional: send this as a reply to an existing message, given its id from get_conversation. Works for both a text message and a document. This is why there is no separate reply script — on Telegram a reply is an ordinary message carrying a reply-to reference.

Which of the two sends ran: "document" when fileBase64 was supplied, otherwise "text".

True once an outgoing bubble matching what was sent, and carrying a server-assigned id, was found in the conversation.

The peer id that was actually opened, read back from the address bar.

The account that actually sent it, read from the app's own account menu rather than assumed from the request. Null if the menu did not expose a name.

True when the send was confirmed by finding the bubble in the conversation afterwards, rather than assumed from the keypress or the button click.

Telegram's server-assigned message id. The script waits for the real integer id rather than the optimistic local one Telegram renders while the send is pending, so this is always usable by delete/react/reply. For a document it also means the upload finished.

The text that was sent, or the caption for a document. Null for a document sent without a caption.

The size Telegram renders on the sent document bubble, read back from the page ("19.0B", "1.2 KB"). Compare it against the bytes you sent to confirm the whole file landed. Null for a text message.

The document's filename, or null for a text message.

The conversation title from the header — echo this to a human, since a peer id is not recognisable.

The message id this was sent as a reply to, or null for a normal message. Evidence-backed rather than echoed: when a reply was requested the script only accepts a sent bubble that actually carries the quoted-message embed, so a reply reference dropped by the attachment dialog fails loudly instead of being reported as done.

Whether an outgoing message with exactly this text (or a document with this filename) was already in the conversation beforehand. Reported, not enforced — resending is legitimate — so the caller decides what to do about a duplicate.