Alerts

The Alerts module wires TradingView's native alert engine to mrD-RSI Pullback so you never miss a signal — even when you are away from the chart, asleep, or running a multi-asset watchlist. Alerts can deliver via mobile push, email, SMS (plan-dependent), browser sound, and webhook (for auto-trading bots and Discord / Telegram notifiers).

This page is the complete reference for the Alerts module: the six built-in alert modes, how to create an alert in TradingView's dialog, the two dedicated Trend Bands alertcondition() entries, webhook integration for bots, the message format for each mode, eight tips for scaling alerts to a watchlist, and the FAQ on TradingView alert quotas.

A sample alert as you would see it on your phone or in Telegram:

🟢 BUY Pullback: BTCUSDT
📊 Timeframe: 60
💰 Entry Price: $50,000.00
📈 RSI: 42.50
🎯 Support (Band): $49,500.00
📉 Low 14: $49,200.00

1. What is the Alerts system?

Alerts let TradingView automatically notify you when a signal fires, via:

• Push notification on the TradingView app (mobile / desktop).
• Email to your registered address.
• SMS (depending on TradingView plan).
• Webhook — POSTs a request to your URL (for auto-trading bots, Discord / Telegram bots, custom systems).
• Sound in browser.

The benefit is straightforward: no need to sit at the chart all day — let alerts run, you will be notified the moment a signal appears.

2. The six built-in Alert modes

The study offers six alert modes — pick one based on need.

Default recommendation: pick the mode matching what you trade. E.g. trading standard Pullback → choose Buy/Sell Pullback. Avoid All — it is noisy.

3. Enable alerts in the indicator

Four steps inside the indicator's settings panel.

Step 1 — Open Indicator Settings

Click the gear icon next to the indicator name on the chart panel.

Step 2 — Find group "ANY ALERT() FUNCTION CALL CONDITIONS"

It is at the bottom of the input panel.

Step 3 — Choose Signals Alerts Type

Dropdown — pick one of the 6 modes from section 2.

Step 4 — Save settings

Close the panel — settings auto-save.

Note: Steps 1–4 only enable trigger conditions in the indicator's code. To make TradingView actually notify you, do the next section.

4. Create an Alert in TradingView

After enabling the mode in the indicator, you must create one alert in TradingView's alert dialog to receive notifications.

Step 1 — Click "Alert" in TradingView

• Desktop: the bell icon on the toolbar.
• Or shortcut: Alt + A.

Step 2 — Choose Condition

• Condition dropdown → choose mrD-RSI Pullback.
• Sub-condition → choose Any alert() function call.

Important: must be Any alert() function call, NOT other conditions in the dropdown.

Step 3 — Choose Trigger

• Once Per Bar Close (default, recommended) — fires only at bar close → no spam, no repaint.

Step 4 — Choose notification channel

• Notify on app — mobile push (need TradingView app).
• Send email — receive email.
• Webhook URL — connect auto-trading bot (see section 6).
• Play sound — browser sound.

Step 5 — Set Alert Name

Use a memorable name, e.g. BTCUSDT 1H Pullback.

Step 6 — Click "Create"

Alert is active. Whenever a signal fires → you get notified.

5. Additional alertcondition() — Trend Bands

Beyond the 6 modes above, the indicator provides 2 dedicated alertcondition() entries for Trend Bands.

A) Trend Bands: Bullish

Fires when RSI Band cloud flips from red → green (bullish trend start).

B) Trend Bands: Bearish

Fires when RSI Band cloud flips from green → red (bearish trend start).

Usage:

• Create alert as usual; in "Sub-condition" → choose one of these instead of Any alert() function call.
• Each condition needs its own alert if you want both.

When to use: when you only care about big trend reversals (cloud flip), not Pullback signals.

6. Webhook integration for auto-trading bots

What is a webhook?

A webhook = TradingView sends a POST request with JSON to your URL when an alert fires. Your URL receives the message → bot processes → places trade automatically.

Step 1 — Get a webhook URL

• Self-hosted — run a server (Node.js, Python Flask, etc.) accepting POST.
• Use a service — 3Commas, Cornix, Wundertrading, Pinescript-Webhook, etc.

Step 2 — In the "Create Alert" dialog

• Tick "Webhook URL".
• Paste your webhook URL.
• In the "Message" field, write JSON in the format your bot expects, e.g.:

{
  "ticker": "{{ticker}}",
  "action": "buy",
  "price": "{{close}}",
  "interval": "{{interval}}",
  "timestamp": "{{timenow}}"
}

Step 3 — Test the webhook

• Save alert.
• Wait for a real fire, or use TradingView's test (if available).
• Check your webhook server log for the received message.

7. Eight tips for using Alerts effectively

Tip 1 — One alert per ticker per mode

Do not create one "All Signals" alert for 10 tickers → flood. Create separate alerts for each (ticker, mode) pair.

Tip 2 — Once Per Bar Close is the golden default

Never pick "Once Per Bar" or "Realtime" for this indicator — you will be spammed every tick. Once Per Bar Close = fires only at bar close.

Tip 3 — Different setup for different style

Tip 4 — Combo with other modes

Create multiple alerts simultaneously:

• Alert 1 (Pullback) → fires on entry signal.
• Alert 2 (Trend Change) → fires when cloud flips → exit everything.

→ You get both entry and exit signals.

Tip 5 — Test alerts before trusting

Before letting alerts run "for real", create one on a chart you are watching live → wait for one fire → confirm notifications arrive correctly.

Tip 6 — Different sound per asset

If you trade many assets, set different sounds per alert → instantly know which asset fired without opening the chart.

Tip 7 — Webhook security

If a webhook connects to a real-trade bot, secure the URL (HTTPS, secret token, IP whitelist). If leaked → others can spoof signals → bot trades wrong.

Tip 8 — Setup alerts for both Pullback + Trend Change

Common workflow:

• Alert mode Buy/Sell Pullback → entry signals.
• Alert mode Trend Change (alertcondition Bullish / Bearish) → exit signals when trend flips.

Ensures you never "diamond hand" a reversed trend.

8. Alert message format

When alerts fire, the message is detailed. The emoji glyphs are intentional — they are the literal output your phone or Telegram bot displays. Sample messages per mode:

Buy/Sell Pullback

🟢 BUY Pullback: BTCUSDT
📊 Timeframe: 60
💰 Entry Price: $50,000.00
📈 RSI: 42.50
🎯 Support (Band): $49,500.00
📉 Low 14: $49,200.00
https://mrd-indicators.com/

Buy/Sell Advanced Pullback

🟢 BUY Advanced Pullback: BTCUSDT
📊 Timeframe: 60 + 240
💰 Entry Price: $50,000.00
📈 RSI Current: 42.50
📈 RSI HTF: 48.00
🎯 Support (Band): $49,500.00
📉 Low 14: $49,200.00
https://mrd-indicators.com/

Trend Change

🟢 BULLISH Trend Change: BTCUSDT
📊 Timeframe: 60
📈 Trend: Bearish → Bullish
💰 Price: $50,000.00
🎯 Support (Band): $49,500.00
https://mrd-indicators.com/

Trend State

STRONG BULLISH State: BTCUSDT
 Timeframe: 60
 RSI: 72.50
 Open: $49,800.00
https://mrd-indicators.com/

Each message contains all the info needed for both bot processing and manual entry.

9. Common mistakes with Alerts

Common questions

Maximum number of alerts? Depends on TradingView plan:

• Free: 1 active alert.
• Pro: 20.
• Pro+: 100.
• Premium: 400.

Trading many assets, you need at least Pro+.

Do alerts expire? Yes. Free / Pro alerts last max 2 months, then auto-expire. Reset or use Premium (forever).

How long is the webhook delay? Usually < 1 sec from bar close. Sometimes 5–10s lag during busy times. Do not build strategies dependent on micro-latency.

Can I auto-trade without a webhook? Some services (like Coinrule, AltSignals) integrate directly with TradingView via API. But webhooks are most universal.

Do alerts repaint? No. The indicator uses barstate.isconfirmed for most signals → alerts only fire on closed bars → never "vanish" after firing.

Final thought

Right alert = no missed signals. Wrong alert = flood. Smart alert = sleep well, trade well.

Alerts are the layer that turns mrD-RSI Pullback from a "watch the chart" tool into a "wait for the bell" tool. Once you wire alerts for your top 5–10 assets and your chosen mode, the workflow becomes: receive notification → run 30-second checklist → enter or skip. That is how the study is meant to be traded long-term.

Where to go next

• The core entry engine the Pullback alert mode watches: Pullback Signals.
• The multi-TF engine the Advanced alert mode watches: Advanced Pullback.
• The "Go to {TF}" warning the alert ignores at runtime: Info Table.
• The 12 golden rules every alert must still pass through: Winrate Tips.
• The general TradingView alert configuration shared across all studies: TradingView Alerts.
• Back to the study overview: mrD-RSI Pullback.