App Logo
Messaging Reduck MCP

How to Send Telegram Messages from Your Personal Account Automatically (no bot, no Telethon, no api_id)

Prompt template

Send "message" from my Telegram account to chat name. Show me the chat's name and wait for my confirmation before you send it.

Get started for free

Overview

Founders, freelancers and community managers want some Telegram messages to go out on their own: a daily report to a team group, a reply drafted by an AI agent, a file to a client when it is ready. They want them to come from their own account, under their own name, not from a bot that nobody has started a chat with. With Reduck, your AI agent or a script sends the message as you, through Telegram Web in your Chrome, after you confirm the chat.

Why it's hard

  • A bot is not you. The Bot API sends as a separate bot account. People must start a chat with it first, and it posts in a group only once someone adds it there.
  • Sending as yourself means the MTProto API. Telethon and Pyrogram send as your account after you create an app at my.telegram.org for an api_id and api_hash, sign in with a phone code, and keep a session file that gives full access to the account. Pyrogram's repository is archived.
  • You handle Telegram's limits yourself. A script must catch FloodWait and wait the seconds Telegram names, and Telegram limits accounts whose sending looks like spam (a PeerFloodError says you are limited).

How Reduck does it

Reduck runs scripts in your own Chrome, where you are already signed in to web.telegram.org:

  1. Find the chat. get_inbox lists your chats with their peer id; your own id is Saved Messages.
  2. Confirm. The agent shows you the chat's title and waits for your yes.
  3. Send. send_message sends the text, or a document with a caption, optionally as a reply to a message from get_conversation. It returns the id Telegram's server gave the message, the account that sent it, and whether the same message was already among the recent ones.

Messages go out under your name, one at a time, with no api_id, no session file and no FloodWait code to write.

How to start

  1. Create a free account at reduck.ai.
  2. Install the Reduck extension in Chrome and pair it.
  3. Connect Reduck to your agent: docs.reduck.ai.
  4. Ask: "Send "{message}" from my Telegram account to {chat name}. Show me the chat's name and wait for my confirmation before you send it."

Sign in to web.telegram.org in that Chrome first.

Ways to send Telegram messages automatically

Method Sends as Needs Limits handled by
Telegram's Schedule Message (in the app) You Nothing, one message at a time, by hand Telegram
Bot API A bot A BotFather token; people start the chat first You
Telethon or Pyrogram script You An api_id and api_hash, a phone login, a session file Your code
Reduck You Telegram Web open in your Chrome One send per run, after your confirmation

Where Reduck is weaker: it is made for messages you confirm, not for sending without a person. A Telethon script on a server sends around the clock with no one watching, and so does a bot.

FAQ

Yes, with a tool that acts as your account rather than as a bot. The usual way is a Telethon or Pyrogram script with an api_id from my.telegram.org. With Reduck, your AI agent or a script calls send_message, which sends from the Telegram Web session in your Chrome: a text, a document, or a document with a caption, optionally as a reply.
A bot is a separate account with its own name: people must start a chat with it first, and it posts in a group only if it was added there. A message from your account carries your name and reaches every chat you can write in, like any message you type.
Send at the pace of a person. FloodWait is Telegram telling a client to wait a number of seconds before the next request; Telethon's FAQ shows how to catch FloodWaitError and wait that long. Reduck sends one message per run, after your confirmation, so it does not burst requests.
Telegram limits accounts that act like spammers, whatever tool sends the messages. Telethon's FAQ says Telegram learns spam patterns and bans suspicious activity, recommends well-established accounts only, and says to check a limit by messaging @SpamBot; a PeerFloodError means you are limited. Messaging many people who did not write first is what gets accounts limited. Use automation for your own chats, groups you are in and people who expect your message.
No. Telethon and Pyrogram need an api_id and api_hash from my.telegram.org, a phone code at the first login, and a session file that gives full access to your account. Reduck uses the Telegram Web session already in your Chrome and never receives your password, code or session.
Yes. send_message sends a document, with a caption if you give text, and returns the id Telegram's server gave the message and the size Telegram holds.
Yes. send_message is marked as needing a person: the agent shows you the chat's title and asks for your confirmation. It also reports whether the same text or file was already among the chat's recent messages, so a retry does not go out twice unnoticed. It refuses a chat your account cannot post in, such as a channel you do not administer.
Your agent or a cron job can call send_message at the time you choose, while your Chrome is open with the Reduck extension. Telegram's own Schedule Message, in the app, needs no tool at all for a one-off message.

Similar use cases

Telegram

Connect Claude to Telegram

Connect Claude, Claude Code or Claude Desktop to your own Telegram account, so it can read, search and summarize every chat, group and channel you are in, history included. Reduck runs in your Chrome, where you are signed in to Telegram Web, and gives Claude the tools as an MCP server. No bot token, no api_id from my.telegram.org, no session file.

Messaging
Telegram

Telegram keyword alerts

Get an alert when a keyword is mentioned in the Telegram groups and channels you are in, even in groups you do not manage. A short script runs the Reduck CLI on a schedule, searches all your chats for your keywords with Telegram's own search, as your own account, and sends you only the new messages. No bot to add, no api_id, no session file.

Messaging
Discord

Schedule Discord messages without a bot

Schedule Discord messages from your own account, with no bot to add and no token to paste. Your AI agent posts your announcements, reminders and DMs at the time you pick, once or every day or week, in every channel you choose, under your own name.

Messaging

Start building not clicking

Get started for free