Get started

Search in scripts for "alert"

TradingHookLibrary "TradingHook" This library is a client script for making a webhook signal formatted string to TradingHook webhook server. buy_message(password, amount, order_name) Make a buy Message for TradingHook.   Parameters:      password : (string) password that you set in .env file.      amount : (float) amount. If not set, your strategy qty will be sent.      order_name : (string) order_name. The default name is "Order".   Returns: (string) A string containing the formatted webhook message. sell_message(password, percent, order_name) Make a sell message for TradingHook.   Parameters:      password : (string) password that you set in .env file.      percent : (string) what percentage of your quantity you want to sell.      order_name : (string) order_name. The default name is "Order".   Returns: (string) A string containing the formatted webhook message. You can use TradingHook WebServer open source code in github(github.com)
Pine Script® library
by dokang
1
The Divergent LibraryLibrary "TheDivergentLibrary" The Divergent Library is only useful when combined with the Pro version of The Divergent - Advanced divergence indicator . This is because the Basic (free) version of The Divergent does not expose the "Divergence Signal" value. Usage instructions: 1. Create a new chart 2. Add The Divergent (Pro) indicator to your chart 3. Create a new strategy, import this library, add a "source" input, link it to "The Divergent: Divergence Signal", and use the library to decode the divergence signals from The Divergent (You can find example strategy code published in our profile) 4. Act on the divergences signalled by The Divergent --- isRegularBullishEnabled(context) Returns a boolean value indicating whether Regular Bullish divergence detection is enabled in The Divergent.   Parameters:      context : The context of The Divergent Library.   Returns: A boolean value indicating whether Regular Bullish divergence detection is enabled in The Divergent. isHiddenBullishEnabled(context) Returns a boolean value indicating whether Hidden Bullish divergence detection is enabled in The Divergent.   Parameters:      context : The context of The Divergent Library.   Returns: A boolean value indicating whether Hidden Bullish divergence detection is enabled in The Divergent. isRegularBearishEnabled(context) Returns a boolean value indicating whether Regular Bearish divergence detection is enabled in The Divergent.   Parameters:      context : The context of The Divergent Library.   Returns: A boolean value indicating whether Regular Bearish divergence detection is enabled in The Divergent. isHiddenBearishEnabled(context) Returns a boolean value indicating whether Hidden Bearish divergence detection is enabled in The Divergent.   Parameters:      context : The context of The Divergent Library.   Returns: A boolean value indicating whether Hidden Bearish divergence detection is enabled in The Divergent. getPivotDetectionSource(context) Returns the 'Pivot Detection Source' setting of The Divergent. The returned value can be either "Oscillator" or "Price".   Parameters:      context : The context of The Divergent Library.   Returns: One of the following string values: "Oscillator" or "Price". getPivotDetectionMode(context) Returns the 'Pivot Detection Mode' setting of The Divergent. The returned value can be either "Bodies" or "Wicks".   Parameters:      context : The context of The Divergent Library.   Returns: One of the following string values: "Bodies" or "Wicks". isLinked(context) Returns a boolean value indicating the link status to The Divergent indicator.   Parameters:      context : The context of The Divergent Library.   Returns: A boolean value indicating the link status to The Divergent indicator. init(firstBarSignal, displayLinkStatus, debug) Initialises The Divergent Library's context with the signal produced by The Divergent on the first bar. The value returned from this function is called the "context of The Divergent Library". Some of the other functions of this library requires you to pass in this context.   Parameters:      firstBarSignal : The signal from The Divergent indicator on the first bar.      displayLinkStatus : A boolean value indicating whether the Link Status window should be displayed in the bottom left corner of the chart. Defaults to true.      debug : A boolean value indicating whether the Link Status window should display debug information. Defaults to false.   Returns: A bool array containing the context of The Divergent Library. processSignal(signal) Processes a signal from The Divergent and returns a 5-tuple with the decoded signal: [ int divergenceType, int priceBarIndexStart, int priceBarIndexEnd, int oscillatorBarIndexStart, int oscillatorBarIndexEnd]. `divergenceType` can be one of the following values: na → No divergence was detected, 1 → Regular Bullish, 2 → Regular Bullish early, 3 → Hidden Bullish, 4 → Hidden Bullish early, 5 → Regular Bearish, 6 → Regular Bearish early, 7 → Hidden Bearish, 8 → Hidden Bearish early.   Parameters:      signal : The signal from The Divergent indicator.   Returns: A 5-tuple with the following values: [ int divergenceType, int priceBarIndexStart, int priceBarIndexEnd, int oscillatorBarIndexStart, int oscillatorBarIndexEnd].
Pine Script® library
by WhiteboxSoftware
2
DiscordWebhookFunctionLibrary "DiscordWebhookFunction" discordMarkdown(_str, _italic, _bold, _code, _strike, _under) Convert string to markdown formatting User can combine any function at the same time.   Parameters:      _str : String input      _italic : Italic      _bold : Bold      _code : Code markdown      _strike : Strikethrough      _under : Underline   Returns: string Markdown formatted string. discordWebhookJSON(_username, _avatarImgUrl, _contentText, _bodyTitle, _descText, _bodyUrl, _embedCol, _timestamp, _authorName, _authorUrl, _authorIconUrl, _footerText, _footerIconUrl, _thumbImgUrl, _imageUrl) Convert data to JSON format for Discord Webhook Integration.   Parameters:      _username : Override bot (webhook) username string / name,      _avatarImgUrl : Override bot (webhook) avatar by image URL,      _contentText : Main content page message,      _bodyTitle : Custom Webhook's embed message body title,      _descText : Webhook's embed message body description,      _bodyUrl : Webhook's embed body direct link URL,      _embedCol : Webhook's embed color,      _timestamp : Timestamp,      _authorName : Webhook's embed author name / title,      _authorUrl : Webhook's embed author direct link URL,      _authorIconUrl : Webhook's embed author icon by image URL,      _footerText : Webhook's embed footer text / title,      _footerIconUrl : Webhook's embed footer icon by image URL,      _thumbImgUrl : Webhook's embed thumbnail image URL,      _imageUrl : Webhook's embed body image URL.   Returns: string Single-line JSON format
Pine Script® library
by wlhm
26
Customizable trailing Stop For Manual EntriesHere's how to create a trailing stop with a manual buy order, on an exchange that does not support native trailing stops. Code can easily be copy+pasted into your normal algos. To set the entry price for your manual trade, specify the bar time when the trade was made. Note that the time you specify needs to correspond to an opening time on your chart--if it's a 3 hour chart, 6 pm or 9 pm will work, but 8 PM will not. It's not as bad as it sounds though, read on :) Per usual I keep multiple options open. Special features in this script: Change time frame for trailing Specify trailing parameter (high, close, hlc3, etc.) Change time frame for stop loss trigger (use a shorter time frame for earlier exits!) Specify trigger parameter (close, low, hlc3, etc.) Remember that annoying issue where you might not be able to precisely specify entry price, because you want to use 3 hour closing prices for your trailing stop but you bought in at 7:41 pm? Add this indicator to a 1 minute chart and set your start time to 19:41, then set the trailing time frame to 3 hours! Next stop is v2, where we take profits along the way before stop loss gets triggered.
Pine Script® indicator
by Gesundheit
9
ICT Levels Breach Scanner (12M Timeframe)Detects and scans for breaches of key Inner Circle Trader (ICT) concepts on the yearly (12M) chart: Swing Lows (3-bar wick pivots), Rejection Blocks (3-bar body pivots), Fair Value Gaps (3-bar inefficiencies), and Volume Imbalances (bullish body gaps ≥0.15%, unmitigated). Features: Tracks active levels with arrays for real-time breach detection (price low below any level triggers alert). Visuals: Blue solid lines (Swing Lows), orange dashed (Rejection Blocks), purple dotted (FVGs), green boxes (VIs)—all extending right. Red triangle + bgcolor alert on breach bar; built-in alertcondition for notifications. Optimized for Pine Screener: Filter stocks (e.g., US exchanges) showing symbols where price has traded below these levels on the latest 12M bar. Usage: Apply to a 12M chart for viz, or add to Screener > Pine tab for multi-symbol scans. Customize gap % or add bearish variants via inputs. Ideal for spotting potential support in long-term trends. ICT-inspired; test on liquid stocks like AAPL/TSLA. Not financial advice.
Pine Script® indicator
by jcg3003
Relative Strength Ratio • Leader Shift Signals## Overview This indicator computes a **Relative Strength (RS) ratio** between your chart’s symbol and a reference symbol (e.g. BTC or index), then overlays an EMA-based trend filter and detects **RS divergences** via RSI on that ratio. It highlights when your symbol is leading vs lagging, and spots potential turning points via bullish/negative divergences. No alerts are forced, you get visual cues (lines & labels) only. --- ## How It Works 1. **RS Ratio** = (base symbol price) ÷ (reference symbol price). 2. Two EMAs (fast & slow) filter trend context and help identify “leader shifts” (when ratio crosses the fast EMA under trend constraints). 3. **RSI on the ratio** is used to detect divergences. We find swing highs/lows in the *ratio* and compare their RSI values: * **Bearish RS divergence**: ratio makes a higher high, but RSI makes a lower high * **Bullish RS divergence**: ratio makes a lower low, but RSI makes a higher low 4. When divergence is confirmed, the script draws connecting lines (and optional markers) on the RS ratio pane to visually flag them. 5. You can customize pivot sensitivity, minimum separation, colors, and toggles for which graphics to show. --- ## Best Usage Suggestions * Use a **reference symbol** that is meaningfully related (e.g. BTC for altcoins, SPX for equities, or a sector index for a stock). The interpretive power comes from seeing relative strength vs a meaningful peer. * On **higher timeframes** (4H, daily), divergences tend to carry more weight. On lower intraday charts, tighten pivot settings to avoid noise. * Prefer divergence signals when the RS ratio is also in a favorable trend (e.g. above its EMA for bullish divergences, below for bearish). Using the trend filter EMAs helps reduce false signals. * Always confirm divergence signals with **price structure, volume, or other momentum indicators**. Divergence is a warning or a hint—not a standalone trigger. * Because RSI on ratio is subject to noise, avoid over-tuning pivots too tight; broader pivot widths give more robust divergence lines. --- ## Inputs & Customization * **Reference Symbol & Timeframe** for ratio comparison * **Fast EMA / Slow EMA lengths** and slope threshold (trend filter) * **RSI length** applied to the RS ratio * **Pivot left / right bars** and **min separation** to define sturdy swings * **Toggle lines / markers** visibility, and pick colors for divergence, ratio, EMAs * Optional “shade” or fill modes (if you have them) --- ## Limitations & Disclaimers * Divergence does **not guarantee** reversals—it often signals **weakening momentum or potential turning zones**, which may not always play out. * In extremely volatile or fast-moving markets, divergence lines may lag or fail. * The script relies on historical data (no future lookahead). Because pivots are confirmed after a few bars, some signals show with delay. * As always: combine with price action, structure, risk management. This is a tool—not a magic eight ball. ---
Pine Script® indicator
by Blk0ut
MTF Squeeze Analyzer - [tradeviZion]MTF Squeeze Analyzer Multi-Timeframe Squeeze Pro Analyzer Tool Overview: The MTF Squeeze Analyzer is a comprehensive tool designed to help traders monitor the TTM Squeeze indicator across multiple timeframes in a streamlined and efficient manner. Built with Pine Script™ version 5, this indicator enhances your market analysis by providing detailed insights into squeeze conditions and momentum shifts, enabling you to make more informed trading decisions. Key Features: 1. Multi-Timeframe Monitoring: Comprehensive Coverage: Track squeeze conditions across multiple timeframes, including 1-minute, 5-minute, 15-minute, 30-minute, 1-hour, 2-hour, 4-hour, and daily charts. Squeeze Counts: Keep count of the number of consecutive bars the price has been within each squeeze level (low, mid, high), helping you assess the strength and duration of consolidation periods. 2. Dynamic Table Display: Customizable Appearance: Adjust table position, text size, and colors to suit your preferences. Color-Coded Indicators: Easily identify squeeze levels and momentum shifts with intuitive color schemes. Message Integration: Features rotating messages to keep you engaged and informed. 3. Alerts for Key Market Events: Squeeze Start and Fire Alerts: Receive notifications when a squeeze starts or fires on your selected timeframes. Custom Squeeze Count Alerts: Set thresholds for squeeze counts and get alerted when these levels are reached, allowing you to anticipate potential breakouts. Fully Customizable: Choose which alerts you want to receive and tailor them to your trading strategy. 4. Momentum Analysis: Momentum Oscillator: Visualize momentum using a histogram that changes color based on momentum shifts. Detailed Insights: Determine whether momentum is increasing or decreasing to make more strategic trading decisions. How It Works: The indicator is based on the TTM Squeeze concept, which identifies periods of low volatility where the market is "squeezing" before a potential breakout. It analyzes the relationship between Bollinger Bands and Keltner Channels to determine squeeze conditions and uses linear regression to calculate momentum. 1. Squeeze Levels: No Squeeze (Green): Market is not in a squeeze. Low Compression Squeeze (Gray): Mild consolidation, potential for a breakout. Mid Compression Squeeze (Red): Moderate consolidation, higher breakout potential. High Compression Squeeze (Orange): Strong consolidation, significant breakout potential. 2. Squeeze Counts: Tracks the number of consecutive bars in each squeeze condition. Helps identify how long the market has been consolidating, providing clues about potential breakout timing. 3. Momentum Histogram: Upward Momentum: Shown in aqua or blue, indicating increasing or decreasing upward momentum. Downward Momentum: Displayed in red or yellow, representing increasing or decreasing downward momentum. Using Alerts: Stay ahead of market movements with customizable alerts: 1. Enable Alerts in Settings: Squeeze Start Alert: Get notified when a new squeeze begins. Squeeze Fire Alert: Be alerted when a squeeze ends, signaling a potential breakout. Squeeze Count Alert: Set a specific number of bars for a squeeze condition, and receive an alert when this count is reached. 2. Set Up Alerts on Your Chart: Click on the indicator name and select " Add Alert on MTF Squeeze Analyzer ". Choose your desired alert conditions and customize the notification settings. Click " Create " to activate the alerts. How to Set It Up: 1. Add the Indicator to Your Chart: Search for " MTF Squeeze Analyzer " in the TradingView Indicators library. Add it to your chart. 2. Customize Your Settings: Table Display: Choose whether to show the table and select its position on the chart. Adjust text size and colors to enhance readability. Timeframe Selection: Select the timeframes you want to monitor. Enable or disable specific timeframes based on your trading strategy. Colors & Styles: Customize colors for different squeeze levels and momentum shifts. Adjust header and text colors to match your chart theme. Alert Settings: Enable alerts for squeeze start, squeeze fire, and squeeze counts. Set your preferred squeeze type and count threshold for alerts. 3. Interpret the Data: Table Information: The table displays the squeeze status and counts for each selected timeframe. Colors indicate the type of squeeze, making it easy to assess market conditions at a glance. Momentum Histogram: Use the histogram to gauge the strength and direction of market momentum. Observe color changes to identify shifts in momentum. Why Use MTF Squeeze Analyzer ? Enhanced Market Insight: Gain a deeper understanding of market dynamics by monitoring multiple timeframes simultaneously. Identify potential breakout opportunities by analyzing squeeze durations and momentum shifts. Customizable and User-Friendly: Tailor the indicator to fit your trading style and preferences. Easily adjust settings without needing to delve into the code. Time-Efficient: Save time by viewing all relevant squeeze information in one place. Reduce the need to switch between different charts and timeframes. Stay Informed with Alerts: Never miss a critical market movement with fully customizable alerts. Focus on other tasks while the indicator monitors the market for you. Acknowledgment: This tool builds upon the foundational work of John Carter , who developed the TTM Squeeze concept. It also incorporates enhancements from LazyBear and Makit0 , providing a more versatile and powerful indicator. MTF Squeeze Analyzer extends these concepts by adding multi-timeframe analysis, squeeze counting, and advanced alerting features, offering traders a comprehensive solution for market analysis. Note: Always practice proper risk management and test the indicator thoroughly to ensure it aligns with your trading strategy. Past performance is not indicative of future results. Trade smarter with TradeVizion—unlock your trading potential today!
Pine Script® indicator
by TradeVizion
19
Bjorgum Double Tap█   OVERVIEW Double Tap is a pattern recognition script aimed at detecting Double Tops and Double Bottoms. Double Tap can be applied to the broker emulator to observe historical results, run as a trading bot for live trade alerts in real time with entry signals, take profit, and stop orders, or to simply detect patterns. █   CONCEPTS How Is A Pattern Defined? Doubles are technical formations that are both reversal patterns and breakout patterns. These formations typically have a distinctive “M” or a “W” shape with price action breaking beyond the neckline formed by the center of the pattern. They can be recognized when a ​pivot fails to break when tested for a second time and the retracement that follows breaks beyond the key level opposite. This can trap entrants that were playing in the direction of the prior trend. Entries are made on the breakout with a target projected beyond the neckline equal to the height of the pattern. Pattern Recognition Patterns are recognized through the use of ​zig-zag; a method of filtering price action by connecting swing highs and lows in an alternating fashion to establish trend, ​support and resistance, or derive shapes from price action. The script looks for the highest or lowest point in a given number of bars and updates a list with the values as they form. If the levels are exceeded, the values are updated. If the direction changes and a new significant point is made, a new point is added to the list and the process starts again. Meanwhile, we scan the list of values looking for the distinctive shape to form as previously described. █   STRATEGY RESULTS Back Testing Historical back testing is the most common method to test a strategy due in part to the general ease of gathering quick results. The underlying theory is that any strategy that worked well in the past is likely to work well in the future, and conversely, any strategy that performed poorly in the past is likely to perform poorly in the future. It is easy to poke holes in this theory, however, as for one to accept it as gospel, one would have to assume that future results will match what has come to pass. The randomness of markets may see to it otherwise, so it is important to scrutinize results. Some commonly used methods are to compare to other markets or benchmarks, perform statistical analysis on the results over many iterations and on differing datasets, walk-forward testing, out-of-sample analysis, or a variety of other techniques. There are many ways to interpret the results, so it is important to do research and gain knowledge in the field prior to taking meaningful conclusions from them. 👉  In short, it would be naive to place trust in one good backtest and expect positive results to continue. For this reason, results have been omitted from this publication. Repainting Repainting is simply the difference in behaviour of a strategy in real time vs the results calculated on the historical dataset. The strategy, by default, will wait for confirmed signals and is thus designed to not repaint. Waiting for bar close for entires aligns results in the real time data feed to those calculated on historical bars, which contain far less data. By doing this we align the behaviour of the strategy on the 2 data types, which brings significance to the calculated results. To override this behaviour and introduce repainting one can select "Recalculate on every tick" from the properties tab. It is important to note that by doing this alerts may not align with results seen in the strategy tester when the chart is reloaded, and thus to do so is to forgo backtesting and restricts a strategy to forward testing only. 👉  It is possible to use this script as an indicator as opposed to a full strategy by disabling "Use Strategy" in the "Inputs" tab. Basic alerts for detection will be sent when patterns are detected as opposed to complex order syntax. For alerts mid-bar enable "Recalculate on every tick" , and for confirmed signals ensure it is disabled. █   EXIT ORDERS Limit and Stop Orders By default, the strategy will place a stop loss at the invalidation point of the pattern. This point is beyond the pattern high in the case of Double Tops, or beneath the pattern low in the case of Double Bottoms. The target or take profit point is an equal-legs measurement, or 100% of the pattern height in the direction of the pattern bias. Both the stop and the limit level can be adjusted from the user menu as a percentage of the pattern height. Trailing Stops Optional from the menu is the implementation of an ATR based trailing stop. The trailing stop is designed to begin when the target projection is reached. From there, the script looks back a user-defined number of bars for the highest or lowest point +/- the ATR value. For tighter stops the user can look back a lesser number of bars, or decrease the ATR multiple. When using either Alertatron or Trading Connector, each change in the trail value will trigger an alert to update the stop order on the exchange to reflect the new trail price. This reduces latency and slippage that can occur when relying on alerts only as real exchange orders fill faster and remain in place in the event of a disruption in communication between your strategy and the exchange, which ensures a higher level of safety. 👉  It is important to note that in the case the trailing stop is enabled, limit orders are excluded from the exit criteria. Rather, the point in time that the limit value is exceeded is the point that the trail begins. As such, this method will exit by stop loss only. █   ALERTS Five Built-in 3rd Party Destinations The following are five options for delivering alerts from Double Tap to live trade execution via third party ​API solutions or chat bots to share your trades on social media. These destinations can be selected from the input menu and alert syntax will automatically configure in alerts appropriately to manage trades. Custom JSON JSON, or JavaScript Object Notation, is a readable format for structuring data. It is used primarily to transmit data between a server and a web application. In regards to this script, this may be a custom intermediary web application designed to catch alerts and interface with an exchange ​API. The JSON message is a trade map for an application to read equipped with where its been, where its going, targets, stops, quantity; a full diagnostic of the current state and its previous state. A web application could be configured to follow the messages sent in this format and conduct trades in sync with alerts running on the TV server. Below is an example of a rendered JSON alert: { "passphrase": "1234", "time": "2022-05-01T17:50:05Z", "ticker": "ETHUSDTPERP", "plot": { "stop_price": 2600.15, "limit_price": 3100.45 }, "strategy": { "position_size": 0.1, "order_action": "buy", "market_position": "long", "market_position_size": 0, "prev_market_position": "flat", "prev_market_position_size": 0 } } Trading Connector Trading Connector is a third party fully autonomous Chrome extension designed to catch alert webhooks from TradingView and interface with MT4/MT5 to execute live trades from your machine. Alerts to Trading Connector are simple; just select the destination from the input drop down menu, set your ticker in the "TC Ticker" box in the "Alert Strings" section and enter your URL in the alert window when configuring your alert. Alertatron Alertatron is an automated algo platform for cryptocurrency trading that is designed to automate your trading strategies. Although the platform is currently restricted to crypto, it offers a versatile interface with high flexibility syntax for complex market orders and conditions. To direct alerts to Alertatron, select the platform from the 3rd party drop down, configure your ​API key in the ”Alertatron Key” box and add your URL in the alert message box when making alerts. 3 Commas 3 Commas is an easy and quick to use click-and-go third party crypto ​API solution. Alerts are simple without overly complex syntax. Messages are simply pasted into alerts and executed as alerts are triggered. There are 4 boxes at the bottom of the "Inputs" tab where the appropriate messages to be placed. These messages can be copied from 3 Commas after the bots are set up and pasted directly into the settings menu. Remember to select 3 Commas as a destination from the third party drop down and place the appropriate URL in the alert message window. Discord Some may wish to share their trades with their friends in a Discord chat via webhook chat bot. Messages are configured to notify of the pattern type with targets and stop values. A bot can be configured through the integration menu in a Discord chat to which you have appropriate access. Select Discord from the 3rd party drop down menu and place your chat bot URL in the alert message window when configuring alerts. 👉  For further information regarding alert setup, refer to the platform specific instructions given by the chosen third party provider. █   IMPORTANT NOTES Setting Alerts For alert messages to be properly delivered on order fills it is necessary to place the following placeholder in the alert message box when creating an alert. {{strategy.order.alert_message}} This placeholder will auto-populate the alert message with the appropriate syntax that is designated for the 3rd party selected in the user menu. Order Sizing and Commissions The values that are sent in alert messages are populated from live metrics calculated by the strategy. This means that the actual values in the "Properties" tab are used and must be set by the user. The initial capital, order size, commission, etc. are all used in the calculations, so it is important to set these prior to executing live trades. Be sure to set the commission to the values used by the exchange as well. 👉  It is important to understand that the calculations on the account size take place from the beginning of the price history of the strategy. This means that if historical results have inflated or depleted the account size from the beginning of trade history until now, the values sent in alerts will reflect the calculated size based on the inputs in the "Properties" tab. To start fresh, the user must set the date in the "Inputs" tab to the current date as to remove trades from the trade history. Failure to follow this instruction can result in an unexpected order size being sent in the alert. █   FOR PINECODERS  • With the recent introduction of matrices in Pine, the script utilizes a matrix to track ​pivot points with the bars they occurred on, while tracking if that ​pivot has been traded against to prevent duplicate detections after a trade is exited.  • Alert messages are populated with placeholders ; capability that previously was only possible in alertcondition() , but has recently been extended to `strategy.*()` functions for use in the `alert_message` argument. This allows delivery of live trade values to populate in strategy alert messages.  • New arguments have been added to strategy.exit() , which allow differentiated messages to be sent based on whether the exit occurred at the stop or the limit. The new arguments used in this script are `alert_profit` and `alert_loss` to send messages to Discord
Pine Script® strategy
by Bjorgum
78