Trading Tools

Alerts

6 min read

What it is

Alerts is a real-time notification engine across three surfaces — a Notification Center for the last 7 days of fired events, a Configure Alerts tab for managing your rules, and a Live Stream that polls the newest fires as they happen. You define rules with 14 trigger types across Price / Indicator / AI Signal / Risk / Custom, set severity (info / warning / critical), pick delivery channels (in-app, Telegram, Discord), and apply a per-rule cooldown so a single condition doesn't fire repeatedly. Filters on the Center tab let you drill by category and severity. Each alert can be test-fired before going live, dismissed individually, or batch marked-read.

How to think about it

Two patterns make alerts worth their weight. First — pair every "do something" automation with a "tell you about it" alert so you find out within seconds, not the next time you open the app. Second — keep critical reserved for actions you'd interrupt dinner for; everything else is warning or info, so the noise floor stays usable.

Step-by-step

  1. Open Configure Alerts and pick a trigger type

    14 triggers across 5 categories. Price: PRICE_ABOVE / PRICE_BELOW / PRICE_CHANGE_PERCENT. Indicator: RSI_OVERBOUGHT / RSI_OVERSOLD / MACD_BULLISH_CROSSOVER / MACD_BEARISH_CROSSOVER / BOLLINGER_SQUEEZE / BOLLINGER_BREAKOUT / VOLUME_SPIKE. AI Signal: AI_SIGNAL_HIGH_CONFIDENCE. Risk: PORTFOLIO_DRAWDOWN / DAILY_LOSS_LIMIT. CUSTOM for engine-emitted rules. Name your rule so future-you knows what it does — "BTC RSI oversold 1h" beats "Alert 1".

  2. Set severity intentionally

    Critical (red) = action required now (PORTFOLIO_DRAWDOWN, DAILY_LOSS_LIMIT, big-move PRICE_CHANGE_PERCENT). Warning (amber) = check soon (most indicator crosses, AI signals). Info (blue) = passive intel (BOLLINGER_SQUEEZE, regular price thresholds). If everything is critical, nothing is. Audit your distribution monthly — if >30% of rules are critical, downgrade the weakest.

  3. Pick delivery channels

    In-App (always on, shows in Notification Center + Layout bell), Telegram (paste Bot Token + Chat ID in Settings → Integrations beforehand), Discord (webhook URL in Settings). You can stack channels — critical alerts typically check all three; info alerts often just in-app.

  4. Set a cooldown that matches the timeframe

    Cooldown in minutes prevents the same rule from re-firing on the same condition. Defaults: scalping rules (1m–5m timeframe) → 5 min cooldown. Swing rules (1h–4h) → 60 min. Position rules (1d) → 360 min. PORTFOLIO_DRAWDOWN typically uses 240 min (4hr) so you get one ping per major leg, not every tick.

  5. Test-fire before you save

    Each rule has a Test button that pushes a sample payload through your delivery channels. Confirm it arrives in your Telegram / Discord / bell BEFORE relying on it. Common test-fail causes: stale Telegram bot token, expired Discord webhook URL, in-app notifications disabled at OS level.

  6. Filter the Notification Center to spot patterns

    TYPE filters: All / Price / Indicator / AI Signal / Risk. SEVERITY filters: All / critical / warning / info. Combine them — Risk + critical shows only your portfolio-level fires. Indicator + warning shows the day's technical setups. The Mark all read button clears the unread counter so the bell badge stays meaningful.

  7. Use the Live Stream tab for active sessions

    Live Stream polls /alerts/stream for the freshest fires. Toggle it off when stepping away to save bandwidth. Useful during high-volatility windows (FOMC, CPI release, large unlock dates) when you want a heads-up rail running while you watch chart context.

Tips & pitfalls

  • Pair every Smart Trade / Grid / DCA / Conditional Bot launch with at least one alert tied to it — "tell me when TP1 fills" or "tell me if drawdown hits 5%". The bot does the work; the alert tells you it happened.
  • PORTFOLIO_DRAWDOWN is the single most important alert most users skip — set it once with critical severity + Telegram delivery, and you have a hard floor on surprise losses.
  • Cooldown is your noise control. If a rule is firing 20× a day, raise the cooldown — you almost certainly cannot act on 20 pings anyway. One actionable ping per timeframe beats 20 ignored pings.
  • AI_SIGNAL_HIGH_CONFIDENCE alerts fire when the MediTrade AI confidence band crosses your threshold (default ~0.75). Use these as a heads-up to review, not as auto-trade instructions — pair with a manual review step before sizing in.
  • Telegram delivery requires a one-time setup in Settings → Integrations (Bot Token + Chat ID). If Test fails, the issue is almost always there, not in the alert rule itself.
  • Alerts ≠ webhooks. Alerts notify YOU. Outbound Webhooks push events to YOUR own Discord/Slack/Zapier. Official Channels broadcast to haythix-owned rooms. These are three distinct distribution surfaces.