> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/models/price-action-model-tm/alerts.md).

# Alerts

Price Action Model Alerts

Missing a setup can be frustrating. The Price Action Model includes built-in alert conditions that integrate seamlessly with TradingView's alert system, allowing you to receive notifications via app, email, or webhook exactly when a mechanical setup forms.

### Available Alert Conditions

* **Bullish Model Formation:**
  * This alert triggers the moment a complete Bullish Price Action Model is validated.
  * **Requirements:** A sell-side liquidity sweep (price breaks below a previous pivot low) must occur, immediately followed by a bullish Change of Character (price breaks structure upward).
* **Bearish Model Formation:**
  * This alert triggers the moment a complete Bearish Price Action Model is validated.
  * **Requirements:** A buy-side liquidity sweep (price breaks above a previous pivot high) must occur, immediately followed by a bearish Change of Character (price breaks structure downward).

### How to Set Up Alerts

1. Open the **Alerts** dialog in TradingView (Alt + A or click the alarm clock icon).
2. Under the **Condition** dropdown, select the **CandelaCharts - Price Action Model** indicator.
3. Choose either the *Bullish Model* or *Bearish Model* from the secondary dropdown.
4. Set your preferred expiration time and notification methods (e.g., pop-up, email, webhook to Discord/Telegram).
5. Add a custom message if desired, and click **Create**.

*Tip: For the most reliable signals, configure your alerts on a timeframe where you have established confluence with the MTF Dashboard.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.candelacharts.com/models/price-action-model-tm/alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.