LucraX has four notification surfaces. Telegram and email are opt-in per user; the in-app surfaces are always on for everyone.
Telegram
The richest channel. You connect a Telegram chat once and the platform pushes trade events to it in near real time.
Setup
Settings → Telegram alerts tab:
- Open the configured LucraX bot in Telegram (
@<BOT_USERNAME>) and press Start. - Get your numeric chat ID from
@userinfobot. - Paste the chat ID into the form, enable the toggle, save.
Events you'll receive
- Trade entry filled (opened position)
- Trade entry failed (entry order rejected)
- Trade exit filled (position closed, any reason)
- Trade exit failed (exit order rejected)
- Liquidation (exchange force-closed the position)
- Circuit breaker halt (daily loss limit or max drawdown tripped)
- Circuit breaker resume (you manually re-enabled)
- WebSocket disconnect from any exchange
- Strategy error (worker crashed or refused to run)
- Strategy halted by breaker (an individual strategy was paused)
Opt-out
Toggle off in Settings or clear the chat ID. The DB columns are
users.telegram_chat_id and users.telegram_alerts_enabled -
the toggle alone is enough.
Same kind of events as Telegram, more reserved set (the high-noise events like WS disconnects are Telegram-only).
Setup
Settings → Email alerts tab. Toggle on. Mail goes to your
account email (users.email); there's no separate address.
Events you'll receive
- Trade entry filled
- Trade exit filled
- Trade exit failed
- Liquidation
- Circuit breaker halt
- Circuit breaker resume
Account-flow emails (verification, password reset) always send and aren't gated by this toggle.
Opt-out
Toggle off in Settings. Column: users.email_alerts_enabled.
In-app banners
Live in the app header on every authenticated page.
- Verify your email - shown when
users.is_verifiedis false. Yellow band with a link to/verify-email. - Trading halted - shown when a circuit breaker has tripped or you've toggled the kill switch. Red band that quotes the halt reason.
Banners persist until the underlying state changes (verify the email, release the halt). They're not dismissible.
In-app toasts
Bottom-right of the screen. Used for one-shot events: a save succeeded, an error happened, a value was copied to clipboard. Auto-dismiss after a few seconds. No persistence - if you miss one, it's gone.
Sentry / ops alerts (internal)
LucraX itself runs a Sentry → Telegram bridge for platform
errors. This is internal - it goes to the operations channel,
not to user accounts. Configured via SENTRY_WEBHOOK_SECRET +
ops-owned TELEGRAM_CHAT_ID. You don't opt in; we don't share
the channel.
Defaults
Both Telegram and email alerts default to off for new accounts. You can run live without ever connecting either, but you'll miss real-time signals about your own trades - most users connect at least Telegram before going live.
Privacy
Telegram chat IDs and email addresses are stored in your user row in plaintext (chat ID is just a number; email is your login). API keys and 2FA secrets are encrypted; preferences are not. See Privacy and security.
