> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quantnomad.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding TradingView Alerts

> How TradingView alerts work with indicators: conditions, trigger frequency, notifications, and the limits to know before you rely on them.

> [!NOTE]
>
> **General TradingView information.** This section describes standard TradingView behavior, not a QuantNomad-specific feature. TradingView updates its interface regularly, so menu names and positions may differ slightly from what you see. When in doubt, check the [TradingView Help Center](https://www.tradingview.com/support/).

An alert tells TradingView to watch a condition on its servers and notify you when it happens, even when your browser is closed. With QuantNomad indicators, the condition is usually one of the indicator's alert conditions, such as a buy or sell signal.

## How an alert is built

Every alert has four parts:

| Part | What it is |
| - | - |
| **Condition** | What to watch: an indicator and one of its alert conditions, or a price crossing a level |
| **Trigger** | How often the alert can fire (for example, once per bar close) |
| **Expiration** | When the alert stops running |
| **Notifications** | How you are notified: app, pop-up, email, sound, or webhook |

## Key concepts

> [accordion] Alerts run on TradingView's servers
>
> Once created, an alert runs on TradingView's servers on the symbol and timeframe you created it on. You don't need to keep the chart open.

> [accordion] Alerts store a snapshot of your settings
>
> An alert saves the indicator's inputs **as they were when the alert was created**. Changing the indicator's settings on the chart afterwards does not update existing alerts. To use new settings, delete the alert and create it again.

> [accordion] Trigger frequency matters
>
> Options such as **Once Per Bar** can fire while the bar is still forming, so a signal can trigger an alert and then disappear before the bar closes. **Once Per Bar Close** only fires on closed bars. See [Confirmed vs Unconfirmed Signals](https://docs.quantnomad.com/guides/confirmed-signals.md).

> [accordion] Plans limit alerts and webhooks
>
> The number of active alerts, and access to features such as webhook notifications, depend on your TradingView plan. Check [TradingView's pricing page](https://www.tradingview.com/pricing/) for current limits.

## Indicator alert conditions

A TradingView script can expose alerts in these ways:

* **Named alert conditions**: these appear by name in the second **Condition** dropdown (for example, a "Buy" condition).
* **Alert function calls**: shown as **Any alert() function call** (or **alert() function calls only** for strategies). The script itself decides when to fire and what message to send.
* **Order fills** (strategies only): fire when the strategy's simulated order fills. You write the message, and can use strategy placeholders such as `{{strategy.order.action}}`.

UT Bot v2 and UT Bot Pro are strategies, so they offer both alert() calls and order fills. Which alerts a script provides is specific to that script. See the alert page for each one:

* [UT Bot v2 alerts](https://docs.quantnomad.com/free-indicators/ut-bot-v2/alerts.md)
* [UT Bot Suite alerts & automation](https://docs.quantnomad.com/premium-indicators/ut-bot-suite/alerts.md)

## Next steps

> [card] [Creating TradingView alerts](https://docs.quantnomad.com/guides/tradingview-alerts.md)
>
> Step-by-step alert setup and message templates.

> [card] [Webhook alerts & automation](https://docs.quantnomad.com/guides/webhooks.md)
>
> Send alerts to external services.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.