# How To Setup Alerts **Alerts** are **extremely useful** for notifying the user when their **chosen condition** has **met** in real-time, which has many **benefits** to a trader's **trading style** such as stopping them from staring at charts for too long and increasing their chances of having a high probability trade when the **right price level or condition hit**. When the alert you've made has hit, **TradingView** will **send** you a **notification** to your **connected mobile** **devices**, it can also send you an **email** and it can appear as a **web hook** to other sources or as a **pop up** within the charts. All of **NVME Trading indicators** have **built-in** **alert conditions** that are **editable** via the **settings** panel so that you can choose what alerts to have and the best part is that you can have **multiple conditions** for **only one alert space**! {% hint style="info" %} Most of our indicators uses the following condition: "Any alert() function call", this allows us to simplify alerts and allow our users to select as many alerts as possible for just one space cost. We also provide some normal alerts for the indicators for those wanting to create web hooks and customise the messages inside the alerts. {% endhint %} ### How To Setup Alerts - "Any Alert() Function Call" Guide In order to **setup an alert**, the user must first **have the indicators on the chart** for extra alert options to appear and the user **need to click** on the icon that looks like an **alarm clock with a plus icon**. The user could also use the **following shortcut** for a quick access: **"CTRL + A"** to open the alert creation panel. ![](/files/-MfdrL-ZO34vG5PKibsX) Once done, the **alert creation panel** will **appear** and you will see a list of **input boxes** that may need filling in. There is only **one thing** that you will need to **change**, which is the **condition input box**. You should **change** the **condition box** from the **asset name** to the **indicator name** that you want the alerts for. By default, the **second condition input box** will be **set to "Any alert() function call"** and you will **not need** to **change** this. ![](/files/-Mfdss6-Qwq0yjCLNtkI) If you have **changed** the **condition box** correctly, it should look like this and then you are **ready** to go and **create your alert**. {% hint style="info" %} Please make sure that you have **items enabled** in the **Alert Actions area** as this will determine how your alert will be displayed to you. Here are my settings that sends alerts to my mobile phone. {% endhint %} ![](/files/-MfdtO00FL_Ivbhr63Dh) {% hint style="danger" %} Warning: Before setting up "Any alert() function call" alerts, the user should visit the indicator's setting panel to see what alerts they have checked and by default many items will be checked, which may be unnecessary for the user. They are usually found at the bottom of each settings panel for all NVME Trading indicators. {% endhint %} ![Custom Alerts for any alert() function calls](/files/-Mfdu6iL2XrnbF_YcV3i) ### How To Setup Alerts - Normal Alerts Guide In order to **setup an alert**, the user must first **have the indicators on the chart** for extra alert options to appear and the user **need to click** on the icon that looks like an **alarm clock with a plus icon**. The user could also use the **following shortcut** for a quick access: **"CTRL + A"** to open the alert creation panel. ![](/files/-MfnP33M_62mBTPISyAp) Once done, the **alert creation panel** will **appear** and you will see a list of **input boxes** that may need filling in. There is only **one thing** that you will need to **change**, which is the **condition input box**. You should **change** the **condition box** from the **asset name** to the **indicator name** that you want the alerts for. By default, the **second condition input box** will be **set to "Any alert() function call"** and you will **need** to **change** this to the specific alert that you want. Also these alerts will **support web hooks** and **custom messages** as they are external rather than internal alerts. ![](/files/-MfnRF6yAX41RF4pNN8N) After selecting the **conditions** that you want, your **alert fields** should look **similar** to the image below depending on what **indicator** you have **chosen to get alerts from**. ![](/files/-MfnbJJ_35c-78fqESsA) ![](/files/-MfnbYm0TXsUZJ9crPgh) {% hint style="warning" %} Note: Please make sure that on the options, you set your alerts to "Once Per Bar Close" for a full confirmation. We have already encoded a bar close confirmation into our scripts but for just in case the alerts become bugged this would be a good way to prevent spammy alerts. {% endhint %} ## Alert Inputs Explained ### Conditions The conditions input field determines when the alert is going to activate. By default there will be many different conditions available that makes use of price data. If you have selected the condition involving the asset name (example: "GBPUSD"), you will a list of conditions popup as shown below. ![](/files/-Mfncq04iyotqwgDSnGc) **Crossing** - This condition is a two way version of crossing up or crossing down that will notify the user if price has crossed the user's inputted price level whether its in an uptrend or not. **Crossing Up** - This condition works in a similar way to Crossing, however it will only trigger if price crosses over the inputted price level rather than crossing under, therefore this alert type should be used to mark higher price levels. **Crossing Down** - This condition works in a similar way to Crossing, however it will only trigger if price crosses underneath the inputted price level rather than crossing over, therefore this alert type should be used to mark lower price levels. **Greater Than** - This condition works by alarming the user that the current price of the selected asset is higher than the price inputted by the user. **Lower Than** - This condition works by alarming the user that the current price of the selected asset is lower than the price inputted by the user. **Entering Channel** - This condition works by placing an invisible horizontal channel within the chart and it will only trigger if the price of the selected asset enters the channel from an out of bounds price level. The upper bound is the maximum price for the channel and the lower bound is the minimum price for the channel, which can be adjusted by the user. **Exiting Channel** - This condition works similarly to entering channel, however the alert will only trigger if the price is out of bounds from the channel (leaves the maximum or minimum zones). These zones can be adjusted by the user. **Inside Channel** - This condition works by checking whether or not price is within the channel, if so an alert will be triggered and sent to the user. The user has the option of customising the upper and lower bound values for the condition. **Outside Channel** - This condition does the opposite of the inside channel condition and checks if the price is outside of the channel, if so an alert will be triggered and sent to the user. The user can also customise the upper and lower bound values for the condition. **Moving Up** - This condition allows the user to get an alert only if price has moved upwards by the amount set. Also, the alert has a specified number of bars lifespan before it expires, which can be changed by the user too. **Moving Down** - This condition allows the user to get an alert only if price has moved downwards by the amount set. Also, the alert has a specified number of bars lifespan before it expires, which can be changed by the user too. **Moving Up (%)** - This condition is the same as moving up but instead uses a percentage to find the final value. **Moving Down (%)** - This condition is the same as moving down but instead uses a percentage to find the final value. ### Options The options input fields determines the behaviour of the alerts, they can change when the alerts are triggered or how many times you get the alert. There are 4 options to choose from. ![](/files/-Mfo-D1VBohyQB83IxgH) **Only Once** - This will set the alert frequency to trigger one time when the condition has met. **Once Per Bar** - This will set the alert frequency to trigger every time the condition is met within one bar but will not take into consideration the confirmation of a bar close. **Once Per Bar Close** - This will set the alert frequency to trigger every time the condition is met and confirmed on the bar close, which is a delayed version of the alert. **Once Per Minute** - This will trigger the alert if the condition has met but it can be triggered again once every minute. ### Expiration Time The expiration time of an alert determines how long its lifespan is. You can either set a specific date for the alert to shut down or you can keep it running forever by enabling Open-ended. ### Alert Actions **Notify On App** - When the alerts are triggered you will get notified on your mobile device with the TradingView application. However you will need to be signed in to the profile with the active alerts. **Show Pop-Up** - When the alerts are triggered you will get notified on TradingView with a pop-up but this will show only when you are on TradingView to analyse. **Send Email** - When the alerts are triggered you will get an email to the email you signed up with on TradingView. **Web hook URL** - When the alerts are triggered, TradingView will send a server-side hook to your designated location either an app or a website and it will showcase to you the message and alert name if you set this up properly. **Play Sound** - A sound will trigger when the alert has fired. **Send Email-to-SMS** - When the alerts are triggered, this will send the alert message to your mobile phone through text messages. ### Alert Name This input field is where you will put the name of your alert, for example "GJ Buy Signal 4HR" using a signal indicator as an alert. ### Alert Message This input field can be used to write a custom message or use placeholders to grab real-time data from the server. Placeholders can be found here: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://alexwalker2003master.gitbook.io/nvme-trading-documentation-1/getting-started-with-nvme/how-to-setup-alerts.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.