How to Set TradingView Alerts: Step-by-Step Guide

Create a TradingView alert by choosing its condition, trigger frequency, expiration, and notification channels, then verify the event in the alert log. Alerts run on TradingView's servers; an open browser is not required. Delivery to a phone, email inbox, or webhook endpoint is a separate step that should be tested.

Choose the alert you actually need

Price alerts monitor a symbol's price condition. Technical alerts can monitor indicators, supported drawings, or script events. A strategy alert can report simulated order fills, calls to alert(), or both. These are not confirmations of a real broker fill.

TradingView now lists Basic, Essential, Plus, Premium, and Ultimate plans. Price-alert quotas, technical-alert quotas, watchlist alerts, expiration, and webhook access are separate features. Check the current pricing comparison for your account instead of relying on old Pro or Pro+ tables. Generating a combined script does not remove TradingView's platform limits.

Set up one observable alert

1. Open the intended symbol and add any indicator or drawing required for the condition.
2. Open Create alert from the chart or Alerts interface. TradingView documents the available entry points in its setup guide.
3. Select the condition explicitly: crossing, crossing up, crossing down, or a supported script event. Check the displayed symbol, value, and any interval field. Do not assume every price alert inherits the chart interval in the same way as an indicator calculation.
4. Choose the frequency supported by that condition. Bar-close evaluation is suitable when your rule requires a confirmed close; it intentionally waits and can miss a transient intrabar crossing.
5. Check expiration and notification settings. Give the alert a name containing the symbol, condition, and intended context.
6. Create it, verify its active state, and observe a qualifying event. Check the log and each delivery channel independently. A nearby price is not guaranteed to trade through your test level.

Understand script snapshots

When a script alert is created, TradingView saves the script, inputs, symbol, and timeframe for its server-side execution. Changing the chart or editing the source later does not update that running snapshot. Recreate the alert after a relevant script or input change.

alertcondition() supplies selectable conditions for indicators. alert() works in indicators and strategies, while strategy order-fill events do not require an alertcondition() call. Some generic indicator alerts can also be created from plotted values. No Pine function creates a running alert by itself; the user creates that in the interface. See the Pine alerts documentation.

For rules involving several timeframes, the script must request and handle the relevant data correctly. Confirmation timing and repainting behavior matter; one alert is not inherently limited to a single source timeframe merely because it runs on one chart interval.

Configure notifications and webhooks separately

Enable the desired mobile or browser permissions and use the same TradingView account on the receiving device. Inspect email filtering if the alert log shows an event but the email is absent.

A webhook sends an HTTP request to an external endpoint; that endpoint must validate and process it. TradingView requires two-factor authentication for webhooks and documents port and timeout restrictions. Valid JSON changes the request content type, but does not make the payload compatible with a broker automatically. Never include account passwords in alert messages. Test with a non-trading receiver before connecting an order workflow. See webhook configuration.

Diagnose missed or excessive events

Check whether the alert is active, expired, stopped, or configured for a different event. Compare the alert's saved inputs with your intended rules. Distinguish a missing event from a failed notification and, for automation, from a rejected order. Closing your laptop is not itself a reason for a server-side alert to stop.

If alerts are too frequent, inspect the actual condition and frequency rather than assuming bar-close mode solves every issue. Review outdated alerts in the manager, stop or delete those no longer needed, and document the settings of recurring setups.

Pineify can help build custom alert logic. Validate the generated source and test the conditions; it cannot guarantee error-free code, profitable signals, unlimited TradingView alerts, or delivery without delay.