Crypto Telegram alerts from Moolish scans and chains

Moolish sends its alerts to Telegram, through a bot that you create and connect yourself. There are two sources of alerts: a Scan Events filter that you save as a preset, and a Chain. Detection runs on the closed bar. Alerts for method events go out right after the bar closes, and a trigger that is only a Candle shape arrives shortly after the close.

Telegram is the alert channel

Telegram is the only place Moolish delivers alerts. The message goes to your own chat, group or topic, through your own bot, so nobody else receives it and nothing about it is shared with other accounts. There is no second delivery path to configure, which keeps setup short: connect Telegram once in Settings, then switch alerts on for the presets and Chains you care about.

An alert names the market, the timeframe and what matched. It is a prompt to open the chart, not an instruction to trade.

Connect your bot in Settings

Alerts need a Telegram bot that belongs to you. Until one is connected, Moolish shows a notice that Telegram is not configured, and preset notifications stay off by default. The connection lives in Settings, at the bottom of the sidebar.

1. Create a bot in Telegram and keep its bot token private. The token lets anyone send messages as that bot.
2. Send a message to the bot, or add it to the group or topic where you want alerts. Moolish lists the groups and topics that the bot has seen, and it shows a short set of steps if the bot has not received any message yet.
3. Open Settings in Moolish and go to the Telegram tab. Enter the bot token and pick the group or topic from the list.
4. Turn on Telegram notifications and choose the notification timing (described below).

Use a chat that is only for Moolish alerts. A busy chat buries the one message that matters, and a dedicated topic in a group lets you mute everything else.

Alerts from a Scan Events preset

In Scan Events you build a filter with one card per timeframe. Each card lists events, Candle shapes or both, and a lookback: the last N candles of that timeframe in which they must appear. Cards are joined with AND or OR. When the filter shows the markets you want, save it as a preset and switch its alert on. The tooltip in the app describes it plainly: a Telegram message when this preset finds new matches after a bar closes.

This is a state alert, not an ordered one. Nothing in Scan Events puts one timeframe’s card after another’s. If the order matters to you, use a Chain.

Alerts from a Chain

A Chain is the ordered tool. You write two to four event steps on the same symbol, and each later step has to happen within a Within window after the previous one. A step can name up to 20 symbols. When the last step lands, the Chain fires once and sends the Telegram message. Chains run on the live stream only, so they have no history scan, and a Candle editor shape cannot be a step. The event chain guide compares the two tools in detail.

Notification timing

For presets, Settings offers two timings. They only change how messages are grouped, not what is detected.

When a Telegram alert arrives

Two steps are easy to confuse. Detection is the scanner noticing that a closed bar carries the event you asked for. Delivery is the message then reaching your chat. Both happen after the bar closes, never during it.

Moolish does not claim instant alerts. For setups that resolve over bars of 15 minutes and longer, the time from the close to your chat is small next to the bar itself. If a strategy depends on seconds, test the path on your own account first.

Limits to know before you rely on it

• Telegram must be connected. With no bot in Settings, the alert switch asks you to connect Telegram instead of turning on.
• One exchange per scan. A preset covers Binance, Bybit or OKX, with Spot, Futures or both. It does not mix exchanges.
• No alerts while the market scope is narrowed. If you narrow the scan by sector, market cap or volume, the app turns the alert switch off and asks you to remove the narrowing first.
• The lookback follows your plan window. The app notes when a lookback is clipped to the number of days your plan allows.
• Closed bars only. A condition on a forming bar is not an event, so an alert is not withdrawn when the next bar starts.
• A setup can notify more than once. A preset reports new matches after each bar closes, so a market that matches again on a later bar can produce another message.

Keeping the volume of messages sensible

The commonest problem with alerts is too many of them. A common event on a fast timeframe across 1,600+ crypto markets would fire constantly, and an alert stream that you cannot keep up with is worse than none. Three habits help.

• Put the rare condition on the slow card. A Buy Setup 9 on the 1D narrows the field before a 15M trigger has to carry the filter alone.
• Choose the exchange and the market type. A scan over Binance Futures alone is much shorter than one over Spot and Futures.
• Match the timeframe to your attention. If you look once a day, an alert whose fastest card is 15M is noise.

Which alert for which job

FAQ