TradingView Alert Script - $10

@Iwori

I'll add the alert layer to your Pine Script without touching the existing trading logic; only new code is appended. One point to clarify: alertcondition() and "Any alert() function call" are two different mechanisms. alertcondition() creates named entries ("Long Entry", "Short Exit", etc.) that you select individually in the alert dialog. The "Any alert() function call" option only appears when the script uses alert(). I can implement either one, or both, so you choose in the UI. Scope: - Named alerts per rule (Long Entry, Long Exit, Short Entry, Short Exit, or whatever your rules define) - Inputs for monitored thresholds, grouped and labeled in the settings panel - Clear alert messages including symbol, timeframe and price - Clean compile, tested by triggering alerts from the TradingView panel To start, I need the current .pine file and the list of conditions that should fire alerts.

@prashanpatel557

Hello, I can add the TradingView alert functionality to your existing Pine Script while keeping the current trading logic unchanged. I have strong experience with Pine Script v5/v6, TradingView alerts, alert conditions, strategy signals, and configurable inputs. I can implement: - Native alertcondition() alerts for your existing signals - Clearly named alerts such as Long Entry, Short Entry, Long Exit, etc. - Alert messages containing relevant dynamic values - No changes to your existing entry/exit logic - Clean Pine Script v5 implementation - Compilation and testing of each alert condition I’ll work directly on your existing .pine file and keep the modification focused only on the alert functionality. Timeline: 1 day Budget: $20 fixed. Please send the Pine Script and I can start immediately. Regards, Prashant Patel

@MqlcoderHub

Hi there, Just a heads-up: "Any alert() function call" only works with alert(), not alertcondition(). So I'll add both. You'll get clearly named alerts like "Long Entry" and "Short Exit," plus the option to set one alert that covers everything. Your logic stays exactly as it is. I'll just add the alert code and a few inputs you can tweak later. Send over the script and I can have it done today. Talk soon, Fasih

@Rsolitario

This task is simple for me; I have experience and have created multiple indicators and strategies for TradingView. I will do this job for you for $10.

@fullstack46138

Hello Houssame Ben, I can add the TradingView alert functionality to your existing Pine Script without changing the current trading logic. I understand the key requirements: Keep all existing logic exactly as-is Add alert functionality using Pine Script v5 Use native alertcondition() Clearly named alerts such as Long Entry and Short Exit User-defined inputs for alert values/thresholds Ensure the script compiles without errors Verify alerts can be created and triggered from TradingView I’ll first review the existing Pine Script and identify the exact conditions already used, then add the alert code without affecting the current signals or calculations. Please send me the .pine file, and I’ll review it and get started. Best Regards, Majid Ul Hassan

@KaleRiddhesh

As per this project I can help you finish alert adjustment and also upgrade this Pine Script v5 -> v6

@naminghn

Hi there, To enable the alert functionality in your existing TradingView Pine Script, I can seamlessly append the alert code while maintaining the integrity of your trading logic. Using Pine Script v5 and the `alertcondition()` function, I'll ensure that you can set alerts directly in the UI with well-named conditions like "Long Entry" and "Short Exit." Additionally, I'll integrate user-defined input fields to give you flexibility in adjusting values or thresholds as needed. Once I compile the script successfully and the alerts are functioning as intended, our job will be complete. Feel free to reach out if you have any specific additional requirements or questions. Regards, Ali

@Synet

Hi, I will add the alert code to your existing Pine Script v5 without touching your core trading logic, making sure you can trigger them directly from the TradingView panel. I will implement the native alert function so you can easily select the Any alert function call option in the interface. Each signal, including Long Entry and Short Exit, will be clearly named and mapped to user defined input fields so you can adjust your threshold values on the fly. I will also format the alert messages to dynamically include the trigger price and timestamp, which gives you instant context without needing to open the chart. I have delivered 4,100+ projects since 2008, including dozens of custom Pine Script indicators and alert integrations. Would you like the alert messages formatted in JSON so you can easily connect them to a webhook like 3Commas or Telegram in the future? Best, Salma Noreen

@kulkonde

Hello, I am experienced pinescript developer I can start immediately and complete this this jonb within 1 hour, you need to send me pinescript and all the remaining details if any, thanks.

@ELGAMLDev

Hi, This is a small, well-defined job and I've done it many times: I add the alert layer at the bottom of your script and don't touch a single line of your existing logic. One thing in your brief needs a quick decision before I start. alertcondition() and "Any alert() function call" are two different mechanisms. With alertcondition(), each rule shows up by name in the alert dialog's condition dropdown ("Long Entry", "Short Exit"), while "Any alert() function call" only works with alert(). The named approach matches what you described, so I'd go with alertcondition() and inputs for your thresholds, unless you'd rather have alert() with dynamic messages. Also, alertcondition() only works in indicators, not strategies. If your script starts with strategy(), I'd use alert() or your order fill alerts instead, and the result is the same for you: named notifications you can set up from the panel.

@braing2

Hello, I built 7 products in 7 days, and I'm passionate about building. I'll add both kinds of alerts at the end of your script: named alertcondition() entries like "Long Entry" and "Short Exit" that you can pick one by one in the alert dialog, and alert() calls with the same names so one "Any alert() function call" alert catches them all. If your script is a strategy, alert() covers everything, since alertcondition() only works in indicators. The thresholds get their own input fields, plus a switch for firing on bar close or intrabar. I'll compile it in v5 and trigger each alert on a live chart before handing it back. What matters most to me is that your logic stays exactly as you wrote it. My last two client projects closed at 5 out of 5, one on Freelancer and one on MQL5. Amul

@abdulawan189

Hi there, I can add clean, reliable TradingView alert functionality to your existing Pine Script without changing your trading logic. I’ll work directly around your current conditions, implement clearly named `alertcondition()` triggers such as **Long Entry, Short Entry, Long Exit, and Short Exit**, and add practical user inputs for adjustable thresholds. I’ll also ensure the implementation follows Pine Script v5 requirements and remains easy to maintain. I’ll compile and test the `.pine` file, verify there are no errors, and make sure the alert conditions appear correctly in TradingView’s **Create Alert** panel. I’ll keep the existing strategy untouched and only add the required alert layer, with clear alert messages and proper configuration so you can confidently use it afterward.

@flowlabdev

Your request mixes two TradingView mechanisms, so I'll add both. alertcondition() gives you named entries in the alert dialog ("Long Entry", "Short Exit"), while "Any alert() function call" only lists alerts sent through alert(). I'll add each rule as a named alertcondition() and also fire alert() with the same message, so either option in the panel works. My plan: 1. Append the alert block at the end of your script without touching the trading logic. 2. Add inputs for the thresholds the alerts watch, with your current values as defaults. 3. Check that it compiles in Pine v5 and that each alert fires on a bar where its rule is true, then send you the .pine file and a short note on creating the alerts. $15, done within a day of getting the script. Is your script an indicator or a strategy? alertcondition() only works in indicators, so for a strategy I'd use alert() calls instead.

@azwa04

Hi, I will start by reviewing your existing Pine Script v5 and adding the alert functionality without changing the current trading logic. I’ll add clear `alertcondition()` rules for each required event, such as Long Entry and Short Exit, with meaningful alert titles and messages. I’ll expose the required thresholds through `input` fields so the alert conditions can be adjusted directly from TradingView. I’ll compile and test the `.pine` script to ensure there are no errors and that each alert appears correctly in the TradingView alert panel. I’ll keep the changes limited to the alert layer so the existing strategy behaviour remains unchanged. Send me the current `.pine` file and I can start.

@jptx265

I'm a solo dev, a true freelancer, so I'm fast, flexible, and focused on quality. I can have this done and ready for your review within 2 hours. Let's get those alerts firing! My Approach: Preserve your existing trading logic exactly as-is. Append alertcondition() calls with clear names (e.g., "Long Entry", "Short Exit"). Add User-Defined Inputs so you can tweak thresholds directly in the script settings without editing code. Ensure the script compiles error-free and triggers correctly in the TradingView UI. Bonus: Since I specialize in automation, I can also show you how to connect these alerts to a Telegram or Discord webhook for instant mobile notifications, not just the standard TradingView popup.

@deepgovindbusin

Hi, I can do it and if you find any problem in my code in future then you can message me any time.

@selaaf

Your alerts should fire from the exact entry and exit rules you already have, with none of that logic touched. First I'd add just the Long Entry alert underneath your existing code, so you can see it compile and appear in the alert panel before the rest follows. alertcondition() shows up as named conditions in the menu, while the "Any alert() function call" choice needs alert() itself, so I'd match whichever you actually want to pick from. Are your entries and exits plain conditions in the script, or do they only live inside strategy calls? Send the script over whenever suits you. Sela

@richardb063

Hi, I can add the alerts while leaving your existing logic untouched, but the detail that decides the implementation is whether you want named alertcondition entries for each event or alert() calls that show up as "Any alert() function call" in the TradingView dialog. Those two behave differently in the alert setup, and picking the wrong one changes how you select alerts later. Do you want each event, like Long Entry and Short Exit, to appear as its own named condition, or is a single "Any alert() function call" option enough? I would append Pine Script v5 alert code after your current logic, add clear names for each trigger, and expose input fields for the thresholds you want to adjust. I would then compile and confirm each alert fires from the panel without altering your entries or exits. Happy to review the details and discuss the best way to implement the solution.

@Caerolix

Adding alertcondition() calls to an already-working Pine Script is a clean, contained edit -- I won't touch your existing trading logic, just layer the alert triggers on top with clear, distinct names for each rule so you always know which one fired. I'll also expose the threshold values as script inputs so you can adjust them later without touching the code again. You'll get back a .pine file that compiles without errors and lets you pick 'Any alert() function call' right away when setting up alerts on the chart. Ready to start now -- this is a same-day turnaround.