Price alert
A direct condition based on the selected symbol’s price—reaching, exceeding or falling below a level you choose.
Alert workflow
A TradingView alert watches a selected market condition and sends a notification when that condition is met. Choose the correct symbol, define the trigger, select how often it can fire and decide where the notification should be delivered.
Alert categories
A direct condition based on the selected symbol’s price—reaching, exceeding or falling below a level you choose.
A condition based on an indicator, drawing, strategy or supported technical value. The chart interval matters because it affects those calculations.
One alert condition applied across symbols in a watchlist, with each symbol monitored independently where the user’s plan supports watchlist alerts.
TradingView alerts run on TradingView’s servers. You can close the browser chart and the alert can still trigger. Delivery still depends on the notification methods you enabled and the channels available for your account and devices.
Setup sequence
A TradingView alert watches a selected market condition and sends a notification when that condition is met. It organizes attention. It does not place an exchange order by itself.
Price alerts watch the selected symbol’s price. Technical alerts watch indicators, drawings, strategies or other supported technical values. Watchlist alerts apply one condition across symbols in a watchlist where the current plan supports that feature.
Open the exact exchange-qualified symbol you intend to monitor. BITSTAMP:BTCUSD and another BTC listing are not automatically interchangeable. Stocks and ETFs need the same care with venue choice.
On Supercharts, use Create alert from the upper toolbar, open the Alert manager on the right toolbar, right-click the chart, or use Alt+A on Windows and Option+A on macOS.
Pick the condition that matches the job: a price level, a crossing, an indicator threshold, a drawing condition or another supported trigger. Keep the condition specific enough that the notification has a clear purpose.
Crossing up and crossing down are different events. If direction matters to the review task, choose the direction deliberately instead of using a generic crossing that fires both ways.
Decide whether the alert should fire only once or can fire repeatedly. A once-only alert is useful for a single level check. A repeating alert needs a clearer naming and review habit so it does not become noise.
Alerts can expire after a set period. Premium and Ultimate plans can use open-ended alerts that remain active indefinitely. Choose an expiration that matches how long the condition still matters.
Choose how you want to be notified: app notification, pop-up, email, sound, plain text or webhook. Not every channel is useful for every plan, device or workflow. Start with a channel you will actually check.
Use a name you can still understand later, such as asset, exchange, timeframe and condition. A clear name makes the Alert manager and alert log easier to review.
Create the alert, then confirm it appears in the Alert manager with the intended symbol, condition and delivery settings. If the setup is new to you, start with a simple price condition before adding technical complexity.
When an alert fires, or when it does not fire as expected, open the alert log. The log is the first place to confirm what TradingView actually delivered.
Return to the Alert manager to edit, pause or delete alerts that no longer match the research task. Changing an indicator’s parameters after an alert is created does not rewrite the alert’s original settings.
Wrong exchange-qualified symbol, vague names, too many repeating alerts, treating every notification as an order signal, and using webhooks before the research alert workflow is stable are the usual early errors.
Move to crypto-specific alert patterns, then decide whether free alert limits are enough. Keep webhook automation as a later bridge, not the first beginner step.
Common mistakes
Monitoring the wrong exchange-qualified listing produces clean notifications about the wrong market.
Names like “BTC alert 3” become hard to audit once several alerts are active.
Webhooks belong in an automation bridge after the research alert workflow is stable. They are not the default beginner path.
When a researched alert should feed a Coinrule rule, use TradingView Alerts to Coinrule. Keep that bridge separate from ordinary research notifications.
Related guides
Practice on the web