Pipe signals to Alerts
Send every future USDⓈ-M signal from a source to your push / Telegram / email / webhook channels. Per-source delivery rules, side filters, symbol whitelist, and quiet hours.
The alert pipe is the non-execution alternative to Auto Trade. Subscribe a signal source and you'll receive a notification — Telegram, web push, browser-tab toast, email — every time a new signal fires from that source. Use it when you want manual control over execution, or when you want to be informed about a source you're not (yet) ready to autotrade.

How it differs from indicator alerts
| Aspect | Indicator alert | Signal source alert |
|---|---|---|
| Trigger | Your own indicator setting crosses a threshold on a specific symbol. | A pre-built signal source emits a signal on any symbol it scans. |
| Symbol scope | One symbol per alert. | All symbols the source covers (filterable). |
| Configuration | You define the indicator + threshold. | You pick the source + side. |
| Best for | Personal setups ("RSI 5m crosses 30 on BTCUSDT"). | Following a curated signal stream. |
Indicator alerts are documented in Alerts → Indicator alerts. This page is about signal-source alerts.
How to subscribe
From the signal detail dialog
- Click any signal in the live feed.
- In the detail dialog, click Set Alert.
- The alert subscription dialog opens, pre-filled with the source, timeframe, and side.
From the Alerts page
/trading-alerts → + New alert → tab Signal source → pick source, timeframe, side, channels.
Subscription fields
| Field | Notes |
|---|---|
| Source | Required. Same options as for autotrade pipe. |
| Timeframes | Multi-select. E.g. 5m + 1h. |
| Sides | Long / Short / Both. |
| Symbol whitelist | Optional. If set, alerts fire only for these symbols. Empty = all. |
| Symbol blacklist | Optional. Skip these. |
| Channels | Multi-select. Web push / Telegram / Email / Webhook / In-app toast. See Alerts overview. |
| Quiet hours | Optional. No alerts during specified hours (your local TZ). |
| Quiet days | Optional. No alerts on specified weekdays. |
| Throttle | Default = no throttle. Optional: max 1 alert per X min per symbol. Helps when a source emits multiple correlated signals quickly. |
| Include AI summary (Ultimate only) | Embed a 2-3 line AI explainer summary in the alert text. |
What the alert payload looks like
Telegram
USDⓈ-M Signal · mrD-RSI Pullback · 5m
LONG BTCUSDT @ 95,230.5
SL : 94,800 (-0.45%)
TP1 : 95,650 (+0.44%)
TP2 : 96,120 (+0.94%)
TP3 : 96,700 (+1.55%)
[ Open detail ] [ Pipe to Auto Trade ]
13:42 UTC · age 8s
Web push (browser)
Title: USDⓈ-M · LONG BTCUSDT @ 95,230 (RSI Pullback 5m)
Body: SL 94,800 · TP1 95,650 · TP2 96,120 · TP3 96,700
Tap → opens signal detail with ?symbol=BTCUSDT deep-link.
Webhook (Ultimate only)
{
"type": "signal",
"hub": "usdm",
"source": "mrd_rsi_pullback",
"timeframe": "5m",
"symbol": "BTCUSDT",
"side": "LONG",
"entry": 95230.5,
"sl": 94800.0,
"tp1": 95650.0,
"tp2": 96120.0,
"tp3": 96700.0,
"generated_at": "2026-05-17T13:42:00Z",
"signal_id": "sig_xxxxxxxx"
}
Headers include an HMAC signature so you can verify the payload was sent by us. See Webhooks.
Delivery latency targets
| Channel | Target latency from signal generation |
|---|---|
| In-app toast | < 200 ms |
| Web push | 1-3 s |
| Telegram | 2-5 s |
| 30-60 s | |
| Webhook | < 500 ms |
If a channel consistently exceeds these latencies, see the per-channel docs (Telegram delivery, Web push).
Plan limits
| Plan | Max signal-source alert subscriptions | Max alerts per day total |
|---|---|---|
| Master | 5 | 100 |
| Premium | 25 | 1000 |
| Ultimate | Unlimited | Unlimited |
Hitting the daily cap pauses NEW alert delivery until the cap resets at 00:00 UTC; existing scheduled alerts still fire.
Snooze
In the alert dialog header, a Snooze 1h quick-action pauses delivery for an hour. Useful when a source is firing too frequently and you want a break without unsubscribing.
Common pitfalls
| Pitfall | Fix |
|---|---|
| Subscribed all sources + all timeframes → 200+ alerts/day → notification fatigue. | Start with one source on one timeframe. Add more only after you adapt. |
| No quiet hours → woken at 03:00 by an ATOMUSDT 5m signal. | Set quiet hours. Or subscribe only to 1h+ timeframes. |
| Webhook URL leaks → spammers send fake signals to your downstream system. | Verify the HMAC signature on every webhook receipt. |
| Email-only on a fast 5m source. | Email lags by 30-60 s; useless for 5m signals. Use push or Telegram instead. |
What's next
- Autotrade pipe — execute the signal instead of just notifying.
- Alerts overview — full alerts subsystem.
- Telegram delivery — set up the bot.
- Web push — browser push setup.