Skip to content
Terminal

Updated

Set up crypto alerts in Telegram

Telegram can carry a crypto alert into a chat you already open. It is a poor place for that alert if the chat is public, if you never pressed Start, or if the bot asked for a key that can move coins. The setup is about choosing the chat and proving the bot may speak there.

This page is about delivery. It does not tell you which coin to watch, and it does not tell you to buy, sell, or hold.

Start the bot yourself

A bot cannot open a private chat on its own. You open it. Telegram's bot features page, opened 2026-10-11, says the first visit shows a Start button. The /start command begins the conversation. A deep link can pass a short parameter at the same time, so a website can open the right bot and hand it a one-time code. You do not paste that code into a group.

The private form is https://t.me/<bot_username>?start=<parameter>. Telegram's example is https://t.me/your_bot?start=airplane, which arrives as /start airplane. The parameter may use letters, digits, underscore, and hyphen. Telegram recommends base64url when the value is not plain text. The parameter can be up to 64 characters. Commands are at most 32 characters, using letters, digits, and underscores.

You press Start in the chat the link opened. That is how the product learns the chat id. If the link is old, start again from the product. A used or expired code is rejected. It does not attach someone else's chat.

Cryptocurrency Alerting's pricing page links Telegram with a user link and a group link, each carrying a start parameter. Its FAQ says one account connects one Telegram destination, and that the company will not ask for a private key. An alert does not need an exchange key that can withdraw.

Send the test first. Cryptocurrency Alerting shows a status such as Not Configured or Verified. The test is not a market move. If it does not arrive, fix the connection before you judge the rule.

Use a private chat for your own alerts

Telegram's Bots FAQ, opened 2026-10-11, separates what a bot can see.

In a private chat, the bot receives your messages. That is the path for a personal alert. A group does not see it.

In a group, a bot with privacy mode on does not see every message. The FAQ limits it to commands meant for it, replies, and a few other cases. Bots do not see other bots' messages. A group shows your alert to every member and uses the stricter rate limit below.

A channel broadcasts to whoever can read it. That is the wrong default for an alert about your own levels. A group deep link uses startgroup instead of start. Telegram's example, https://t.me/your_bot?startgroup=spaceship, asks you to pick a group, and the update arrives as /start@your_bot spaceship. Use that only when you mean to add the bot to a group you administer.

Stay inside the length and the rate

The Bot API page, opened 2026-10-11, says sendMessage text is 1 to 4,096 characters after entities are parsed. A longer text is rejected. An alert does not need 4,096 characters. The useful message names the coin, the rule, the price, the source, and the time.

The Bots FAQ states the sending limits. In one chat, avoid more than one message per second. Short bursts may pass, and then the API returns HTTP 429. In a group, a bot may not send more than 20 messages per minute. For bulk notifications, a bot may not broadcast more than about 30 messages per second, unless it uses paid broadcasts.

Paid broadcasts, turned on in BotFather, raise the ceiling to 1,000 messages per second. Each message above the free 30 per second costs 0.1 Stars. Only successful messages are billed. The bot needs at least 100,000 Stars and at least 100,000 monthly active users. That is a large-broadcast feature. One private chat, with a cooldown on each rule, stays under one message a second. A rule that fires on every check can still hit HTTP 429. The messages fail even though the price condition was real.

If the bot is offline, Telegram does not keep updates forever. The Bot API says incoming updates are stored until the bot reads them, and they are not kept longer than 24 hours. An outage longer than that can drop the update on Telegram's side. The alert product still needs its own record of the fire. The chat is a copy.

Quiet belongs on the alert

Muting a Telegram chat mutes that bot, including a later test. It does nothing for email if you left email on.

TradingView's notification-schedule page, opened 2026-10-11, blocks every listed channel outside the hours you set, and it still writes the trigger to the log. A Once only alert that trips while the schedule is closed can notify once when the schedule is open again and the condition is met.

A cooldown is a different control. Cryptocurrency Alerting's FAQ says a cooldown of 1 hour means at most one notification an hour from that alert. The FAQ does not describe a nightly quiet window. The cooldown limits repeats of one rule. It does not limit the clock, so different alerts can still arrive together at 3:00 AM.

Keep the text factual. Name the price and where it came from. Robinhood's price-alert article says its notices are not a recommendation to buy, sell, or hold. A short chat message is an easy place to blur that line.

A checklist

  1. Create the alert with a percent or a price you can read, and a cooldown you can read.
  2. Open Telegram from the product's link, and press Start in that private chat. Forward the link into a group only if you intend the group to receive the alerts.
  3. Send the test, and confirm it is labeled as a test.
  4. Confirm the bot did not ask for a private key, a seed phrase, or an exchange key that can withdraw.
  5. Set quiet hours in the alert product if it offers them. Mute the chat only when you want every message from that bot to wait.

Terminal connects Telegram with a one-time link, asks you to press Start, and uses a test message to show the chat is connected. The test is not a market move. The alerts that follow describe the price. They do not tell you to buy, sell, or hold.

FAQ

Do I add the bot to a channel for my own alerts?

No. A channel broadcasts to its readers. Your own alerts belong in a private chat you opened with Start. Telegram documents start for private chats and startgroup for groups.

What is the message length limit?

The Bot API, opened 2026-10-11, limits sendMessage text to 1 to 4,096 characters after entities are parsed. A message past the limit is rejected. The page does not say the text is trimmed.

Why did a burst of alerts fail?

In one chat, Telegram asks bots to stay near one message per second, then returns HTTP 429. In a group, the cap is 20 messages per minute. A cooldown on each rule keeps a personal watchlist under those limits. Paid broadcasts, at 0.1 Stars above 30 messages a second, require 100,000 monthly active users. They are not the path for one person's alerts.

Sources

Opened 2026-10-11.

Start free