Choose no-code alerts when an existing script exposes your exact entry and exit conditions. Choose Pine Script when you want to define and test the rules in TradingView. Choose a native MT5 Expert Advisor when the rules should run inside MT5 and use its account and market information.
A native MT5 EA that calculates its own signals and submits its own orders does not need PineConnector. For a TradingView-to-MT5 path, PineConnector routes your alert instructions to its EA. None of these paths creates a trading edge; automation executes the rules you supply.[1][2]
Part 5 of 8 in From discretionary to automated trading. Previous: Define the strategy rules. Next: Check the backtest's assumptions.
What are you choosing besides a programming language?
You are choosing where the rules run, which data they can see, where they are tested and who maintains them. Begin with the written specification from Part 4. A missing rule stays missing when you change tools.
| Path | Rule owner | Testing and operation |
|---|---|---|
| A. No-code alerts | Existing script or exposed alert conditions | Verify the author's rules and actual alerts; keep the receiving MT5 setup running. |
| B. Pine Script | Your editable TradingView script | Test the strategy simulation, then the alert-to-broker path; maintain both. |
| C. Native MT5 EA | Your MQL5 implementation | Use MT5 Strategy Tester, then broker demo verification; keep that EA's terminal running. |
A no-code alert is not automatically a backtestable strategy. A Pine indicator also needs a suitable strategy implementation if you want a TradingView strategy report. TradingView's broker emulator and MT5's Strategy Tester test their respective implementations, not the complete external webhook route.[3][4]
When do no-code alerts fit the written rules?
No-code means you configure an existing alert interface. Someone still owns the underlying logic. PineConnector's guide identifies three starting points:[5]
For a webhook route, confirm that your TradingView plan includes webhooks and that two-factor authentication is enabled.[15] Those prerequisites apply even when you write no code.
- A strategy offers “Order fills only”. The events come from TradingView's simulated orders. Check whether each fill means an entry, a full exit, a partial exit or a reversal.
- The script exposes PineConnector message inputs. Follow the author's supported alert method and inspect the generated message. A field named “License ID” alone does not establish compatibility.
- The indicator exposes named conditions. Confirm what each condition means. A condition called “Sell” might mean close a long, open a short or reverse. Those actions require different handling.
If none applies, chart arrows do not supply an alert interface. Keep the process manual or obtain an implementation that exposes the required conditions. Generic price alerts can express simple comparisons, but their existence does not establish your full strategy.
TradingView multi-condition alerts combine up to five supported conditions on one symbol for Plus plans and above. TradingView excludes strategies and scripts using alert() from that feature.[6] Treat it as a condition-combining feature; this guide has not verified an end-to-end PineConnector implementation with it.
Keep the order meaning explicit. Sending every strategy “sell” fill as a new sell request can open an unintended short when the strategy only meant to close a long. TradingView's simulated quantity is also not automatically a MetaTrader lot amount or loss budget.[5]
Acceptance line for path A: the exposed conditions reproduce the written rule, the observed messages distinguish entries from exits, and each intended receiving demo account shows the expected action and protection. If an essential condition is not exposed, the path has not passed.
When should you write or adapt Pine Script?
Use Pine when TradingView is the intended home for your market conditions and you need editable rules, dynamic message values or a TradingView strategy simulation. You can add alerts to your own source or have a programmer implement the specification. The PineConnector alert guide covers the alert setup.[7]
The PineConnector Pine Script converter accepts supported Pine Script v5 and v6 indicators and strategies. It creates a separate Pine copy with PineConnector settings; it does not produce an MQL5 EA. Unsupported or ambiguous code stops the conversion rather than supplying a completed implementation.[8]
Conversion still requires review. Alerts start off and the documented entry-volume default is 1 lot. The converter does not reproduce TradingView's position sizing or copy its simulated stops and targets into protective broker orders. Its adapter does not resynchronise broker and simulated positions.[8] Confirm the intended size and protection before enabling anything.
A comment on an entry does not isolate every generated closing or reversal command. Read the exact command and the converter's scope notes. Do not treat conversion as proof that the London example's one-position requirement has been enforced in MT5.
Pine's strategy.position_size is simulated state. A chart can show no position while the broker still has one, or show a position after a broker stop has closed it.[3][8] A requirement based on actual account exposure therefore needs receiving-account checks and reconciliation.
For ongoing maintenance, retain the source, input values, rule version and expected cases. TradingView alerts use saved script and input snapshots, so recreate the affected alert after editing the implementation.[9]
Acceptance line for path B: the chosen script version matches the condition worksheet, entry and exit messages match the complete specification, and demo reconciliation explains every expected signal and broker result. Compilation alone would not establish those outcomes.
When should the rules live in a native MT5 EA?
Choose a native EA when the implementation should read the broker account directly, work from the broker's available market data or operate without a TradingView alert dependency. MQL5 is the implementation language; MetaEditor is used to create, compile and debug the source. MetaQuotes also supplies an MQL5 Wizard that assembles EAs from selected modules.[1] Whether those modules express your exact specification still needs checking.
Test that implementation in MT5's Strategy Tester. Select a modelling mode that can represent the rule's timing, record costs and account settings, and reserve a separate period for verification. “Every tick based on real ticks” uses broker-collected ticks where available; missing tick data can still require generated ticks.[4][10] A historical tester run is not a demo broker execution.
A direct native EA needs its own running terminal and appropriate trading permission. Use a suitable computer or VPS; MetaQuotes virtual hosting is another option for EAs compatible with its restrictions.[1][11] PineConnector Edge hosts MT5 with the PineConnector EA and does not host third-party EAs.[12]
Acceptance line for path C: the EA reproduces the intended conditions on its chosen data, respects actual account position scope, and demo orders, deals and resulting positions agree with its logged decisions. Confirm behaviour after a restart and when an order is rejected before relying on the implementation.
How would the same London rule work on all three paths?
Illustrative example, not a recommendation. Keep the Part 3 conditions: EURUSD H1, confirmed closes, and bars opened 07:00–10:00 inclusive in Europe/London time. EMA(50) must exceed EMA(200) and its own value five bars ago.
At least one of the last three closed bars must have a low at or below that bar's EMA(50). The current close must exceed its EMA(50) and the previous high. Keep the manual news veto, no unresolved prior entry, no matching long in simulation and each receiving account, and at most one entry request per London calendar day.
The stop reference is the lowest low of five closed bars minus 2 pips (0.0002). The target is the signal-bar close plus twice its distance above the stop. Plan US$100 loss at the stop in a USD account, with a receiving-account entry-spread limit of 2 PineConnector pips. At 16:00 London, request a close and verify the broker result; the request time does not establish that the account is flat then. Actual loss can exceed the planned amount.[13]
| Path | Implementation of that rule | Boundary to resolve |
|---|---|---|
| A. No-code | Use an existing script only if it exposes these conditions, timing, daily limit and separate exit action. Confirm that its message fields can carry the calculated levels. | A generic crossing alert is incomplete. Keep any missing condition manual or choose another path. |
| B. Pine | Implement the conditions, daily counter and close request in Pine; specify the broker request using Part 4's explicit units and levels. | Simulated state does not enforce actual exposure. Reconcile the receiving accounts and verify broker protection separately. |
| C. Native EA | Reimplement the conditions, London-time conversion, account checks, sizing and requests in MQL5 using the chosen broker data. | Broker H1 bars and EMA values may differ from TradingView. Record and test that data change instead of claiming identical signals. |
The native route preserves the decision specification, but it may use a different price series. If identical TradingView inputs are essential, that dependency belongs in the specification and may favour the Pine route. Moving languages does not erase it.
Complete the eight-question path worksheet
Write one answer and one piece of evidence for each question. An unanswered requirement is a reason to retain a manual step or complete the specification.
-
Are the exact entry and exit conditions already exposed?
Answer: __________. If yes, path A is a candidate. List the actual menu options and actions. A chart marker alone is insufficient. -
Do you have editable source, or an owner who can maintain it?
Answer: __________. Choose B for custom TradingView logic when you can maintain Pine or commission the work. Otherwise document the dependency on the script author. -
Which rules require actual broker information?
Answer: __________. List positions, pending requests, spread or other account inputs. C can place the logic in MT5; A and B need an explicit receiving-account check for each such requirement. -
Is a TradingView alert dependency acceptable?
Answer: __________. A and B need the configured alert path. If the strategy must run without it, consider C. -
Which data and tester should define the evidence?
Answer: __________. B suits a TradingView strategy simulation. C suits an MT5 EA tested on the selected broker history. A depends on the existing script's testing facilities. -
Who owns hosting and recovery?
Answer: __________. Name the operator and environment. For A or B, choose the supported PineConnector hosting path. For C, choose hosting that can run that particular EA. -
How many accounts receive each decision?
Answer: __________. Record every destination and its symbol, account type and ownership scope. A broker result on one account does not verify another; sharing a PineConnector License ID sends signals to all its connected accounts.[14] -
Who will approve a changed rule and repeat its checks?
Answer: __________. Name the source owner, reviewer and time available for maintenance. If nobody owns changes, keep the workflow manual until that responsibility is assigned.
What must stay running, and what can you stop maintaining?
TradingView runs created alerts on its servers. Closing the browser is different from stopping the alert. The receiving MetaTrader terminal and EA still need to run.[2] With PineConnector Edge, the hosted service runs MT5 with the PineConnector EA; your own computer can be off after setup.[15] You still own the strategy, alerts and broker-account checks.
For self-hosted PineConnector, follow the supported Windows installation and DLL requirements. Its documented installation workflow does not support MetaQuotes' built-in VPS. That restriction is specific to this PineConnector setup; it is separate from native EAs compatible with MetaQuotes virtual hosting.[16]
Edge's EA uses fixed defaults, so a rule that depends on changing an EA input needs an explicit compatibility check. Choosing hosted MT5 does not grant arbitrary MQL5 hosting or editable EA settings.[12]
What does choosing a path fail to prove?
Choosing a path does not verify the strategy, message units, order scope or broker outcome. Keep condition evaluation, alert trigger, webhook delivery, PineConnector processing, EA request, broker acceptance, fill and resulting position separate. Accepted requests do not by themselves establish fills.[17][18]
Adding another EA to the same account also changes the ownership problem. Review account type and each EA's scope before combining them. An ordinary close command's documented comment filtering is not evidence that every partial-close, reversal or account-wide control is isolated the same way.[13]
When commissioning an implementation, supply the entries, exits, broker symbol, sizing rules and demo acceptance cases. Ask for editable source and instructions for the alert type or EA installation. The finished condition and rule worksheets make that brief concrete.[19]
What is the next step after choosing?
Record the selected path and unresolved requirements, then work through Part 6's backtesting checks. For a TradingView-to-MT5 implementation, follow Part 7's connection, demo-order and per-signal reconciliation procedure. A native EA needs equivalent condition-to-broker evidence from its own logs; PineConnector connection tests do not apply to that direct path.
Reviewed 23 September 2026 against primary documentation accessed on that date. No trading account was tested and no Pine Script or MQL5 code was compiled.
Related reading
- From discretionary to automated trading: the series guide
- Define the whole strategy before choosing an implementation
- TradingView backtesting: costs, fills and out-of-sample checks
- Verify the TradingView-to-MT5 demo path
Sources
- MetaQuotes – Automated trading, accessed 23 September 2026.
- PineConnector – Frequently asked questions, accessed 23 September 2026.
- TradingView – Strategies, accessed 23 September 2026.
- MetaQuotes – Testing trading strategies, accessed 23 September 2026.
- PineConnector – Connect your strategy, accessed 23 September 2026.
- TradingView – Multi-condition alerts, accessed 23 September 2026.
- PineConnector – Add alerts to your script, accessed 23 September 2026.
- PineConnector – Pine Script converter, accessed 23 September 2026.
- TradingView – Alerts, accessed 23 September 2026.
- MetaQuotes – Real and generated ticks, accessed 23 September 2026.
- MetaQuotes – Virtual hosting, accessed 23 September 2026.
- PineConnector – PineConnector Edge, accessed 23 September 2026.
- PineConnector – Syntax: explicit units, position commands and filters, accessed 23 September 2026.
- PineConnector – Multi-Instance Signals, accessed 23 September 2026.
- PineConnector – Getting started, accessed 23 September 2026.
- PineConnector – MetaTrader 5 installation, accessed 23 September 2026.
- PineConnector – Test your setup, accessed 23 September 2026.
- MetaQuotes – Basic principles: orders, deals and positions, accessed 23 September 2026.
- PineConnector – Recommendations, 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.
