Keep your strategy
Automate entries and exits from your existing Pine Script or indicator alerts without rebuilding your trading logic.
Your TradingView strategy places trades in your MT5 broker account. Control lot size, entries, exits, trailing stops and risk limits with the AlgoWay EA.
14-day free trial for eligible new connections · One account per regular subscription · Unlimited alerts
Use your own MT5 terminal or choose CloudMT5 for hosted execution.
Example workflow
Standard plan requires a running MT5 terminal. CloudMT5 is a separate hosted service.
Automate entries and exits from your existing Pine Script or indicator alerts without rebuilding your trading logic.
Set lot multipliers, symbol mapping and execution modes independently for each connected MT5 account.
Use supported stop-loss, take-profit, partial close, trailing and reverse instructions through the compatible AlgoWay EA.
Use Clone Mode to distribute alerts to individually configured terminals and accounts rather than creating duplicate alerts.
Run the AlgoWay EA in your own always-on MT5 terminal, or choose the separate hosted CloudMT5 service without maintaining a local terminal or VPS.
Inspect webhook messages and execution results in Logs and Test; use demo accounts to validate your broker's lot and symbol rules.
Trade without maintaining MT5 yourself: CloudMT5 is a separate hosted service, not included in the $7 standard MT5 plan. The standard plan requires an always-on terminal running the AlgoWay EA.
Prop firm routes: Explore FTMO, FTUK and Atlas Funded. MT5 availability does not automatically authorize every automation method or account program.
Choose your MT5 setup: run the EA yourself for $7/month, or use the separate CloudMT5 service for $14/month with no terminal to maintain.
Compare with PineConnector >>One regular subscription covers one connected trading account, with unlimited TradingView alerts and symbols.
Monthly billing. One account with execution settings, logs and test tools.
Annual billing for the same regular connection.
Available for eligible new connections. Test your strategy and account setup before subscribing.
Clone Mode supports a main route and up to two additional configured routes; each destination requires its own active connection unless covered by All-in-One. All-in-One is $69/month or $690/year. Broker and TradingView charges are separate.
An MT5 terminal cannot receive a TradingView webhook as an order on its own. AlgoWay receives the alert and passes the trading instruction to the Expert Advisor connected to your broker account. The EA must remain online for execution, and the broker ultimately decides whether the lot size and order parameters are valid.
AlgoWay gives each MT5 route a webhook identifier, while the AlgoWayWS-MT5 Expert Advisor handles execution inside the terminal. The EA connection, symbol mapping, trade mode and safety settings matter just as much as the alert itself.
MT5 orders are placed by the EA under the broker account logged into the terminal. The terminal and EA must remain running and connected.
TradingView contracts do not automatically equal MT5 lots. Set the EA Lot Multiplier for the intended units, then check broker minimum and step size.
Reverse, Hedge and Opposite behavior, session limits, SL/TP, trailing and drawdown protections are configured for the MT5 execution workflow.
The connection has two parts: an AlgoWay webhook destination and an Expert Advisor running in the trading terminal. Treat the UUID, the logged-in broker account and the EA status as a single configuration that must agree.
In AlgoWay, add a TradingView source and MetaTrader 5 destination. Copy the unique webhook UUID from the route.
Use AlgoWayWS-MT5 on supported Windows terminals or the Ubuntu/Wine native-socket build where appropriate. Attach it to a chart in the correct logged-in MT5 terminal.
Set the UUID inside EA Inputs and confirm the connected state in MT5 Experts logs before sending any order.
Inspect the broker symbol volume_min, volume_step and volume_max. Set Lot Multiplier and the desired sizing model; do not assume a TradingView quantity means lots.
Paste the AlgoWay webhook URL into TradingView, add structured JSON to Message and test a minimal order in a demo account. Verify both AlgoWay logs and the MT5 Trade/History tabs.
A TradingView strategy can supply its chart symbol, order direction and strategy quantity. The example intentionally contains no hard-coded order ID; order matching requires identifiers generated by the strategy and handled consistently by entries and exits.
{
"ticker": "{{ticker}}",
"order_action": "{{strategy.order.action}}",
"order_contracts": "{{strategy.order.contracts}}"
}TradingView substitutes the placeholders when the alert fires. The EA receives quantity through the route but interprets it according to its Lot Multiplier and broker contract settings. Validate the resulting MT5 lot volume in a demo terminal.
Each MT5 account has its own lot step, symbol names and trading rules. Set the AlgoWay EA's quantity multiplier, symbol mapping and position mode for that account; confirm stop and target placement on a demo before trading live. For hosted execution, review the separate CloudMT5 service.
A strategy emits a EURUSD long alert using a single TradingView contract-size convention. Account A is a small retail account with a conservative lot multiplier and a tighter daily loss limit; Account B uses a different broker suffix and smaller position size. Configure independent AlgoWay routes and EA settings for each account instead of sending one fixed lot value everywhere.
First verify that both terminals are connected, then send a demo entry followed by a flat alert. Only after those two actions agree with your intended exposure should you test absolute SL/TP, trailing, sessions and clone routing. Clone Mode distributes a signal; it does not remove broker-specific volume or execution rules.
Check EA connection, Algo Trading permission, the UUID and Experts log before changing the strategy.
Review Lot Multiplier, strategy units, broker contract size and volume step. Never correct this by guessing.
Review absolute versus relative exit fields, EA Inputs and the broker retcode; invalid stops can be rejected.
The EA must run in the MT5 instance connected to the actual broker account. A local install cannot execute in an unrelated VPS terminal.
Compare the AlgoWay webhook log with the MT5 Experts and Journal tabs, then the broker order history. A successful HTTP delivery without a connected EA cannot prove that the broker executed a position.
MT5 does not receive TradingView webhooks natively. AlgoWay receives the alert and sends it to the connected MT5 EA for broker execution.
You need a running, connected MT5 terminal. A VPS is useful for unattended operation, but an already reliable always-on terminal also works.
AlgoWay offers an Ubuntu/Wine-oriented MT5 EA build with native socket/TLS transport. Use the compatible build for that environment.
The EA applies sizing and multiplier rules while the broker enforces volume steps and contract specifications. Validate the conversion using a small demo order.
Yes. Telegram is a separate signal source in AlgoWay, with its own parsing and route settings; MT5 remains the execution destination.
The MT5 EA guides cover connection and sizing; the invalid-stops article explains why correct TradingView prices can still fail at a broker.
Keep your TradingView strategy and choose how your MT5 terminal will run.
If you are choosing an MT5 execution bridge, see the PineConnector alternative for MT5 and the side-by-side PineConnector comparison. For MT5 alongside cTrader and other supported destinations, read our TradersPost alternative.