Your indicator paints a clean buy signal, you watch price take off, and the indicator does nothing about it. That is the limit of an indicator: it shows you what is happening, but it never places a trade.
To request broker orders from those signals, the script needs usable alerts and an explicit mapping from each signal to an entry, exit or reversal. With editable Pine source, you can add the required alerts. Without it, compatibility depends on the alert interfaces the author exposes.
Indicator vs Strategy: What Actually Changes
In Pine Script, an indicator and a strategy are different tools. An indicator, declared with indicator(), calculates values and plots them. A strategy, declared with strategy(), can open and close simulated positions and produce a backtest.
You do not always need to rewrite an indicator as a backtestable strategy to add alerts. PineConnector processes the messages sent by the chosen TradingView alert method. Define the intended entries, exits, size and broker protection before configuring that route.
Step 1: Turn Your Signals Into Clear Rules
Write each condition as an observable true-or-false rule, including the input, comparison, lookback, timeframe and evaluation moment. Distinguish an event such as a crossing from a state that can remain true across several bars.
For example, if you go long when a fast line crosses above a slow line:
Illustrative condition specification: the fast line was at or below the slow line on the previous closed bar and is above it on the current closed bar. Define the opposite event separately. These comparisons specify a crossing; they are not executable code.
If your entry depends on a level instead, such as RSI crossing above 30, the same idea applies. The goal is one clear condition for each entry and each exit, with nothing left for a human to interpret.
Step 2: Attach explicit entry instructions
Use the Add alerts to your script guide for the alert method that matches your indicator or strategy. An alert() message is built in the script. Strategy order-fill messages use the author's alert_message setup and its required placeholder. Do not enable both event types unless the design explicitly needs them.
The chart ticker from syminfo.ticker is not necessarily the broker symbol. Supply the exact receiving-account symbol, including its suffix. Use explicit sizing and stop units; a broker request still requires verification.
Illustrative message structure: LicenseID,buy,BrokerSymbol,vol_lots=LotSize,sl_pips=StopPips. Replace every placeholder with the intended destination, permitted demo lot size and stop distance. The complete message belongs in the selected TradingView alert's Message field when that alert method exposes it; for alert(), build it in the script instead. Add secret= privately if Signal Authentication is enabled.
Waiting for a confirmed bar close avoids some intrabar changes. It does not eliminate every source of repainting, future-information leakage or repeated qualifying bars.
Step 3: Decide how positions close
Specify whether an opposite condition should close a position, open another, or request both actions. A sell entry is not a close-long instruction. PineConnector documents separate close commands and combined closelongopenshort / closeshortopenlong requests. Check both actions of a reversal on demo; a combined request does not establish that both completed.
Close on Reverse is an EA setting to review in a self-hosted setup and, on Edge, in Portal → Edge → EA Settings (EA Settings guide). Changing a local EA does not change the hosted one, and applying a hosted change restarts the terminal for about a minute. Verify the hosted settings and exact command scope before choosing the behaviour.
Use the Syntax guide to specify size and broker protection. Loss-based sizing requires an explicit stop in the same message. A simulated strategy stop is not automatically a broker stop. A comment label does not establish isolation for every close or reversal command.
If you cannot edit the script
Check for a strategy's Order fills only option, author-supported PineConnector message inputs, or named entry and exit conditions. A chart arrow and a field called License ID are not enough to establish compatibility. Use Connect your strategy to choose the documented path.
Strategy fills belong to TradingView's simulation. A sell fill may close a long; mapping every buy or sell fill to a new entry can create an unintended position. The {{strategy.order.contracts}} quantity is not automatically MetaTrader lots, cash loss or a percentage. Do not substitute it for a sizing parameter without a verified unit conversion and exit/reversal mapping.
If the author provides per-order messages, follow that setup, including {{strategy.order.alert_message}} where required. If the script exposes no suitable alert method, retain the manual workflow or obtain an implementation with the needed interfaces.
Add the alert and verify a demo outcome
Confirm webhook access on your TradingView plan and enable two-factor authentication. For indicator alert() calls, select Any alert() function call; for a strategy using those calls, select alert() function calls only. Follow the script's documented method if it instead uses order fills.
In TradingView's Webhook URL field, use the URL without angle brackets:
https://webhook.pineconnector.comFollow the two-stage demo test: check connection messaging, then one demo order. Reconcile the TradingView alert, PineConnector processing, MT5 request and broker orders, deals and position. Verify size and accepted broker SL/TP. Resolve an unknown outcome before repeating a request.
Recreate affected TradingView alerts after script or input edits. A completed build or a received webhook does not establish correct trading behaviour.
Next step: complete the written rule and its demo acceptance cases, then choose the supported alert method. PineConnector Edge provides hosted MT5 with the PineConnector EA when that hosting path fits the specification. Automation executes rules; it does not create a trading edge.
Reviewed 23 September 2026 against primary documentation accessed on that date; Edge EA Settings updated 6 October 2026. No trading account was tested and no Pine Script or MQL5 code was compiled for this update.
Sources
- PineConnector – Connect your strategy, accessed 23 September 2026.
- PineConnector – Add alerts to your script, accessed 23 September 2026.
- PineConnector – Syntax, accessed 23 September 2026.
- PineConnector – Edge, accessed 23 September 2026.
- PineConnector – Getting started, accessed 23 September 2026.
- PineConnector – Test your setup, accessed 23 September 2026.
- TradingView – Repainting, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
