Telegram Alerts & Bot
Two-way Telegram bot for alerts and quick commands
Predite talks to Telegram in two ways: it can push your alerts to your Telegram chat, and it runs a two-way bot you can message to pull your portfolio and the latest signals on demand. There is also an optional public channel that broadcasts delayed signals.
Personal alerts
Any alert rule you create in Predite can be delivered straight to Telegram instead of, or alongside, email.
To turn it on:
- •Message @PrediteBot on Telegram and it will give you your numeric Chat ID.
- •In the dashboard settings, enable the Telegram toggle and paste that Chat ID.
- •On any alert rule, choose Telegram as a delivery channel.
From then on, whenever a rule matches a fresh signal you get a message with the market, the direction (YES or NO), the edge in percentage points, the model confidence, the platform, and a link back to the dashboard.
The two-way bot
You can also message the bot to pull data on demand. Send it these commands:
- •/start — introduces the bot and explains how to connect
- •/connect YOUR_API_KEY — links your Predite account; requires a Bot-plan API key from the API settings page (see Public API)
- •/portfolio — your current positions
- •/signals — the top five Expected Value signals right now
- •/whales — the five most recent whale moves
- •/help — the list of commands
Connecting with /connect stores your Chat ID for you, so it doubles as a quick way to wire up personal alerts.
The public signals channel
Predite also operates an optional public Telegram channel that posts Expected Value signals on a deliberate delay, followed by the WIN or LOSS result once each market resolves. It is a free taste of the scanner — subscribers on a paid plan get every signal in real time inside the app. This channel is configured by the Predite team and may not be active in every environment.
Good to know
- •Personal alerts and the public channel are written in English.
- •Your Chat ID is just a number that identifies your chat with the bot — it is not a password, but there is no reason to share it.
- •Prefer machine-readable data for your own tooling? Use the Public API instead.