TradingView alerts (2026): server-side rules, webhooks, templates & common mistakes
TradingView alerts guide 2026: server vs client alerts, multi-condition setups, webhooks, naming templates and a reliability checklist.
- Server-side alerts are valuable because they keep running even when your browser is closed.
- Reliability comes from simplicity: fewer alerts, good naming, and testing on one market/timeframe before scaling.
- If you use webhooks, test your payload and add guardrails (duplicates, latency, market closed).
Alerts are one of TradingView’s best features: they turn charting into a notification system.
The classic failure mode is creating too many alerts and losing trust in them.
Alert types
Depending on plan/features, you’ll see:
- price alerts (levels, breaks),
- indicator alerts (RSI, MA, MACD…),
- script/strategy alerts (Pine Script),
- composite conditions (multiple signals).
Rule of thumb: one alert = one action (enter, exit, invalidate).
Multi-conditions: reduce noise
A reliable structure is:
- one primary condition (breakout),
- one filter (trend),
- one context check (volume/volatility),
- a clear trigger rule (bar close vs intrabar).
Explicit rules beat complicated rules.
Webhooks: automation with discipline
Webhooks make sense if you connect to:
- your server,
- an automation tool,
- a bot/external platform.
Minimal webhook checklist:
- stable payload format,
- alert identifier (to dedupe),
- clear trigger mode (e.g. bar close),
- receiving-side handling (idempotency, errors).
Templates: standardize what works
Build a small “library”:
- 3 core alerts (entry / stop / exit),
- naming standard (instrument + timeframe + signal),
- message standard (instrument, timeframe, context).
Templates make your system reproducible.
Reliability checklist
- I know why this alert exists (and the action it triggers).
- I tested it on one market/timeframe before duplicating.
- I keep the number of active alerts low and readable.
- I know if it triggers intrabar or on close.
- If webhook: I have a dedupe guardrail.
One reliable alert beats twenty noisy alerts.
Create 3 core alerts on one instrument (entry, invalidation, exit) and verify they fire as expected.
Open TradingViewFAQ
Do alerts work if I close TradingView?
Yes if they are server-side alerts. They keep running on TradingView’s side and notify you via the chosen channel.
Why do my alerts trigger too often?
Usually because conditions are too broad, the timeframe is wrong, or you’re triggering intrabar without a close filter.
What is a TradingView webhook used for?
To send an HTTP message to an external service (bot, server, automation) when an alert triggers.
How do I avoid duplicates?
Name alerts consistently, use close-based triggers when appropriate, and handle idempotency on the receiving side.