> 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/sfp-model/alerts.md).

# Alerts

SFP Model Alerts

### Available Alerts

Four independent alert conditions are available:

* **SFP Formed (Bullish)** — fires when a new bullish SFP pattern is first detected
* **SFP Formed (Bearish)** — fires when a new bearish SFP pattern is first detected
* **SFP Confirmed (Bullish)** — fires when a bullish SFP receives confirmation close
* **SFP Confirmed (Bearish)** — fires when a bearish SFP receives confirmation close

{% hint style="info" %}
When “High Probability SFPs” is enabled, alerts only trigger for SFPs that pass the channel/trendline interaction filter.
{% endhint %}

### Setup Alerts

To set up alerts using the CRT Model on TradingView, follow these steps:

1. **Create a New Alert**\
   Click the **“+ Alert”** button located at the top of your TradingView chart interface.
2. **Set the Condition**\
   In the **"Condition"** dropdown menu, select **CRT Model** as the indicator you want to trigger the alert.
3. **Choose the Timeframe**\
   Under the **“Interval”** setting, choose your **preferred timeframe** (e.g., 1H, 4H, 1D) based on your trading strategy or the timeframe you want to monitor.
4. **Configure Alert Expiration (Optional)**\
   In the **“Expiration”** section, you can optionally set a date and time for when the alert should stop triggering.
5. **Name Your Alert (Optional)**\
   In the **"Alert Name"** field, provide a **custom name** for your alert. This helps you identify it easily, especially if you're managing multiple alerts.
6. **Create the Alert**\
   Once all settings are configured, click **“Create”** to activate the alert.


---

# 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/sfp-model/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.
