How to Use AlgoWayWS-MT5 EA 2.14 for TradingView to MT5 Webhook Automation

AlgoWayWS-MT5 EA is the MetaTrader 5 execution bridge for AlgoWay. It connects the AlgoWay platform to your MT5 terminal and lets structured signals from TradingView alerts, Telegram signals, manual webhook tests, or other supported sources become real MT5 trading actions.

This page is the current user-facing guide for the AlgoWayWS-MT5 EA 2.14 workflow. The file name still contains v206 because it originated from an earlier documentation cycle, while the content now reflects the current EA build and current AlgoWay platform direction: TradingView to MT5 webhook automation through AlgoWay and the AlgoWayWS-MT5 Expert Advisor.

All EA settings in this guide are named exactly as users see them in the MetaTrader 5 Inputs tab. Internal MQL variable names are intentionally not used for EA settings.

The complete execution route is:

TradingView alert -> AlgoWay webhook -> AlgoWayWS-MT5 EA -> MetaTrader 5 broker account

This guide explains what the EA does, how webhook JSON fields are interpreted, how trade modes work, how SL/TP and trailing rules are applied, and how to troubleshoot the most common MT5 execution problems.

Last updated: 2026-07-27 • Author: AlgoWay

Start Here: Current Setup and Support Guides

This page explains the EA behavior and JSON logic. For installation and platform setup, use the dedicated guides below.

Why AlgoWayWS-MT5 EA Exists

TradingView is powerful for charting, Pine Script strategies and alerts, but TradingView does not directly execute trades inside your MetaTrader 5 broker terminal. MetaTrader 5 can execute trades through Expert Advisors, but it needs a reliable way to receive the signal from outside.

AlgoWayWS-MT5 EA closes this gap:

• TradingView creates the signal;
• AlgoWay receives the webhook alert and validates the message;
• AlgoWayWS-MT5 EA keeps the MT5 terminal connected to AlgoWay;
• MetaTrader 5 executes the order through your broker account.

Competitors describe the same market need as a TradingView-to-MT5 bridge, webhook-to-EA connector, or alert automation layer. AlgoWay focuses this workflow around a dashboard, structured JSON, WebSocket EA delivery, logs, and multi-source signal routing.

What the EA Does and What It Does Not Do

The AlgoWayWS-MT5 EA is an executor. It receives commands routed by AlgoWay and performs trade actions in MetaTrader 5.

The EA can help with:

• opening BUY or SELL positions;
• closing positions with flat commands;
• modifying SL/TP where supported by the message and current route;
• handling trade modes such as Reverse, Hedge, Opposite and Inverse;
• applying SL/TP, trailing, breakeven and profit lock rules;
• mapping TradingView tickers to exact MT5 broker symbols;
• respecting configured position size mode, session filters and limits;
• writing useful logs in MetaTrader 5.

The EA does not create the strategy. It does not guarantee profit. It does not fix a bad TradingView strategy, invalid signal logic, broker spread, slippage, closed market, insufficient margin or unsupported broker settings.

Runtime Conditions in MetaTrader 5

Before expecting the EA to execute orders, confirm these MT5 conditions:

• AlgoWayWS-MT5 EA is attached to a chart.
• MT5 Algo Trading is enabled.
• The EA is allowed to trade in its chart properties.
• DLL imports are enabled if required by the current WebSocket EA setup.
• The correct AlgoWay webhook UUID is entered in the EA inputs.
• The EA shows connected status in the MT5 Experts log or chart status.
• The broker symbol is visible in Market Watch and receiving quotes.

If MT5 returns Error 4752, the EA is probably blocked by algorithmic trading permissions. Read: How to fix MT5 Error 4752.

Connecting the EA to AlgoWay

The key connection value is shown in MT5 as Your Algoway Webhook here. It identifies which AlgoWay webhook route belongs to this MT5 terminal.

Name shown in MT5 Inputs	Meaning	Example
Your Algoway Webhook here	AlgoWay webhook UUID or the full https://algoway.co/<uuid> webhook URL. EA 2.14 extracts the UUID from the full URL automatically.	b7534616-6c8c-4582-8af4-7c143d323231
MAGIC_NUMBER	Magic number used by the EA to identify and manage only its own positions.	1973

If the EA is connected to the wrong webhook, valid alerts can reach AlgoWay but never reach the intended MT5 terminal. Do not attach two active EA instances to the same webhook: the single-instance guard keeps only one instance active.

Complete EA 2.14 Inputs Reference

The names below match the labels visible in the MetaTrader 5 Inputs tab.

Connection and Execution

Symbols Mapping

Use TView Ticker N1 through TView Ticker N5 together with Broker Ticker N1 through Broker Ticker N5. Each pair replaces the TradingView symbol with the exact MT5 broker symbol.

Position Size Mode

EA Based Trailing

EA Based SL and TP

Martingale and Trade Limits

Sessions, Daily Window and Auto-Close

Telegram Notifications

Core TradingView to MT5 JSON Fields

A basic AlgoWay message for MetaTrader 5 contains four main fields:

Field	Example	Purpose
platform_name	metatrader5	Tells AlgoWay to route the command to MetaTrader 5.
ticker	EURUSD	Defines the trading symbol. It may need mapping to the broker symbol.
order_contracts	0.10	Defines the size value before final sizing mode and coefficient logic.
order_action	buy	Defines the action: buy, sell, flat, modify or mode-specific action.

Basic market order:

{
  "platform_name": "metatrader5",
  "ticker": "EURUSD",
  "order_contracts": 0.10,
  "order_action": "buy"
}

TradingView Strategy Alert Example

For a TradingView strategy alert, use TradingView placeholders. TradingView replaces them when the alert fires.

{
  "platform_name": "metatrader5",
  "ticker": "{{ticker}}",
  "order_contracts": "{{strategy.order.contracts}}",
  "order_action": "{{strategy.market_position}}",
  "price": "{{close}}"
}

If this message reaches AlgoWay but MT5 does not trade, check the EA connection, symbol mapping, lot size, trade mode, broker session, margin and MT5 logs.

Supported Trade Actions

Action	Meaning	Typical use
buy	Open or process BUY-side command	Long entry
sell	Open or process SELL-side command	Short entry
long	Directional value treated as BUY where supported	TradingView strategy state mapping
short	Directional value treated as SELL where supported	TradingView strategy state mapping
flat	Close position logic	Exit signal or partial close workflow
modify	Modify an existing position	Update SL/TP by identifier

Trade Modes: Reverse, Hedge, Opposite and Inverse

The dropdown shown as Reverse / Hedge / Opposite / Inverse defines how the EA behaves when a new signal arrives while a position already exists on the same symbol.

Mode	Behavior	Best use case
Reverse	One-side model. The EA closes the opposite side and opens or keeps the new side according to signal logic.	Simple TradingView strategy automation where one side should be active.
Hedge	BUY and SELL can exist at the same time if the account supports it.	Hedging systems and independent long/short logic.
Opposite	The latest signal controls direction. The current position can be closed and the opposite side opened.	Strategies that flip immediately from long to short or short to long.
Inverse	Incoming direction is inverted before execution logic. BUY becomes SELL, SELL becomes BUY.	Counter-signal workflows or inverse strategy execution.

Detailed mode guide: How AlgoWay handles opposite trading signals.

Position size: Lots / Risk% / Balance%

The same order_contracts value can mean different things depending on the value selected in Position size: Lots / Risk% / Balance%.

SIZE_LOTS

order_contracts is treated as lots before coefficient and broker validation.

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "EURUSD",
  "order_contracts": "0.10"
}

SIZE_RISK_PERCENT

order_contracts is treated as percent risk of equity. This mode requires a usable Stop Loss because the EA needs stop distance to calculate position size.

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "EURUSD",
  "order_contracts": "1.0",
  "stop_loss": "100"
}

SIZE_BALANCE_PERCENT

order_contracts is treated as percent of balance. This is not the same as risk-by-stop-loss mode.

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "EURUSD",
  "order_contracts": "5.0",
  "stop_loss": "100"
}

Coefficient for work with Lots

Coefficient for work with Lots multiplies the final size derived from order_contracts.

• 1 - keep the computed or provided size.
• 0.5 - use half the size.
• 2 - double the size.

Always test final lot size in a demo or small-volume environment before live trading. Wrong coefficient values can create invalid volume errors or oversized positions.

Order filling type: AUTO, FOK or IOC

• Auto Mode - lets the EA select a filling mode supported by the broker symbol.
• FOK - Fill or Kill. The requested volume must be filled completely or the order is rejected.
• IOC - Immediate or Cancel. The broker may fill the available part and cancel the remainder.

Use Auto Mode unless the broker or prop firm explicitly requires another mode. MT5 retcode 10030 means the selected filling mode is not supported for that symbol.

Symbol Mapping: TradingView Ticker vs MT5 Broker Symbol

TradingView and MT5 brokers often use different symbol names. Enter the TradingView value in TView Ticker N1 and the exact MT5 symbol in Broker Ticker N1. The same rule applies to pairs N2 through N5.

TradingView ticker	MT5 broker symbol
DE40	GER40
XAUUSD	GOLD
US30	DJ30
EURUSD	EURUSD.a

If the symbol is not found, the trade will not open. Always confirm the exact broker symbol in MT5 Market Watch.

SL/TP Model A: Levels from JSON

Model A means the alert message itself sends Stop Loss, Take Profit or trailing fields.

Exact SL/TP Prices

{
  "platform_name": "metatrader5",
  "order_action": "sell",
  "ticker": "XAUUSD",
  "order_contracts": "0.05",
  "sl_price": "2055.50",
  "tp_price": "2038.00"
}

Distance-Based SL/TP

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "BTCUSDT.P",
  "order_contracts": "0.10",
  "stop_loss": "150",
  "take_profit": "300"
}

Priority rule: if sl_price or tp_price are set and non-zero, price levels should take priority. Otherwise distance fields such as stop_loss and take_profit are used.

SL/TP Model B: Levels from EA Inputs

Model B means the EA applies internal SL/TP values from the Inputs tab.

• Use fixed SL/TP (pips) inside EA - enables fixed EA distances for new entries.
• Internal SL distance in pips - fixed Stop Loss distance.
• Internal TP distance in pips - fixed Take Profit distance.
• Do not place SL in MT5 - suppresses Stop Loss placement.
• Do not place TP in MT5 - suppresses Take Profit placement.

When Use fixed SL/TP (pips) inside EA is enabled, the EA uses the internal distances for that entry instead of the alert-provided distance values. Exact behavior still depends on the selected PIP type and broker stop restrictions.

PIP type: AUTO/TRADINGVIEW/PERCENT

The dropdown shown as PIP type: AUTO/TRADINGVIEW/PERCENT controls how distance values are interpreted.

• PIP_AUTO - follows broker digits and point logic.
• PIP_TRADINGVIEW - Forex commonly uses 1 pip = 10 broker points; other symbols commonly use 1 pip = 1 broker point.
• PIP_PERCENT - SL, TP, trailing, breakeven and profit-lock distances are treated as percentages of the relevant price.
• POINTS - each distance unit is treated as one broker point. This value exists in the EA 2.14 dropdown even though the visible label lists the three original modes.

Wrong distance interpretation is a common cause of invalid stops and MT5 Error 4756.

Trailing Stop from JSON and EA Inputs

Trailing can be enabled per trade with trailing_pips.

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "GBPUSD",
  "order_contracts": "0.10",
  "stop_loss": "120",
  "trailing_pips": "80"
}

If trailing_pips is present, trailing is enabled for that trade. If it is absent, the EA uses Enable Trailing SL, Trailing Step in pips and Start trailing after N pips, 0 = immediate.

Delayed Trailing Activation with trail_points

trail_points allows trailing stop to start only after the trade moves a specified number of pips into profit.

• trail_points = 0 - trailing starts immediately after the position opens.
• trail_points = 50 - trailing starts only after 50 pips of profit.

{
  "platform_name": "metatrader5",
  "ticker": "SP500",
  "order_action": "buy",
  "order_contracts": "4",
  "trailing_pips": "20",
  "trail_points": "50"
}

In this example, the trailing step is 20 pips, but trailing starts only after the trade moves 50 pips in profit.

Breakeven

Breakeven logic moves Stop Loss to the entry area after the trade reaches a configured profit distance.

• Enable Breakeven - enables breakeven logic.
• Move SL to BE after X pips profit - defines when breakeven activates.

Breakeven is useful when a strategy should remove open risk after the market moves in the intended direction.

Profit Lock

Profit Lock is more advanced than basic breakeven. It can move Stop Loss so that a defined amount of profit is protected after the trade reaches a trigger.

• Enable Profit Lock factor - enables profit lock logic.
• Delta trigger - profit threshold that activates the feature.
• Profit Lock after XX pips - profit distance the EA tries to protect after activation.

In simple terms: first the trade reaches the trigger, then the EA moves SL to protect the configured profit.

Partial Close with Close Size Mode

The setting shown as Close size: Lots / Percent % controls whether the EA closes positions by lots or by percentage of the initial position volume.

• CLOSE_LOTS - order_contracts in a flat signal is treated as lots.
• CLOSE_INITIAL_PERCENT - order_contracts in a flat signal is treated as percent of the initial position.

{
  "platform_name": "metatrader5",
  "ticker": "SP500",
  "order_action": "flat",
  "order_contracts": "25"
}

If the initial position was 4.00 lots and Close size mode is CLOSE_INITIAL_PERCENT, this command closes 25% of the initial position, which is 1.00 lot.

close_side for Hedge Workflows

close_side is used with flat to close only one side where supported.

{
  "platform_name": "metatrader5",
  "order_action": "flat",
  "ticker": "EURUSD",
  "close_side": "long"
}

• long or buy - close BUY-side positions.
• short or sell - close SELL-side positions.

If close_side is used with buy, sell or modify, treat it as invalid. It belongs to close/flat logic.

Modify Existing Positions

modify is used to update an existing position instead of opening a new one. The position must be identified by comment or tv_order_id depending on your route.

{
  "platform_name": "metatrader5",
  "order_action": "modify",
  "ticker": "ETHUSDT",
  "comment": "TV#12345",
  "stop_loss": "140",
  "take_profit": "280"
}

If no matching position is found, the modification cannot be applied.

Martingale

Enable increasing the lot after a losing trade activates martingale sizing. Lot increase coefficient defines the multiplier for the next step. This is a high-risk feature and should be tested carefully before live use.

Do not enable martingale just because it exists. Use it only if the trading system was designed and tested for this risk model.

Trade Limits, Sessions, Daily Window and Auto-Close

Trade Limits

• Max daily loss in % - closes all EA positions and blocks new trading for the rest of the calculated trading day after the threshold is reached. Zero disables it.
• Max drawdown per trade in % - closes an individual EA position when adverse price movement from its open price reaches the configured percentage. This is a price-drawdown calculation, not account-equity risk. Zero disables it.
• Max positions, if 0 = no limit - limits all open positions belonging to the EA magic number.
• Max positions per direction, if 0 = no limit - separately limits BUY and SELL positions.
• Max spread in points, 0 = disabled - blocks new entries when the current Ask-Bid spread exceeds the selected broker-point value. Closing actions remain available.

Fixed UTC Sessions

The three session switches are always evaluated in UTC:

• London (07:00-16:00)
• New York (12:00-22:00)
• Tokyo (22:00-07:00)

At least one selected session must be active when an entry command arrives. The enabled sessions are combined: an entry is allowed when the current UTC time is inside any enabled session and also inside the Daily Trade Window.

NY session: Winter or Summer

NY session: Winter or Summer controls the trading-day reset used by daily-loss calculations and Auto-Close:

• WINTER - reset at 22:00 UTC.
• SUMMER - reset at 21:00 UTC.

This setting does not move the fixed New York (12:00-22:00) session row.

Daily Window Time Mode and Daily Trade Window

Daily Window Time Mode selects which clock is used to evaluate Daily Trade Window:

• UTC - coordinated universal time. This is the default and preserves older EA behavior and existing setup files.
• Broker Time - MT5 trading-server time, the same time basis used in broker trade history.
• Local Time - the Windows clock of the computer or VPS running MT5.

Daily Trade Window uses HH:MM-HH:MM. Example: 01:30-23:30. A range that crosses midnight is valid, for example 23:30-21:30.

For verification, the MT5 Experts log writes the current UTC, Broker and Local timestamps together with the selected window mode in the [SCHEDULE] record. When using Local Time, make sure the Windows/VPS clock and time zone are correct.

Autoclose mode and minutes before end

Autoclose mode can close EA positions near the end of the calculated trading day or trading week. minutes before end defines how early the closing process begins. The day boundary comes from NY session: Winter or Summer.

If a signal is rejected by a session, Daily Trade Window, spread or position limit, the webhook is not necessarily broken. The EA followed the configured Inputs.

Telegram Notifications from the EA

The EA can send Telegram notifications about AlgoWay connection loss and recovery.

• Telegram notify for AlgoWay disconnect
• Telegram chat id
• Telegram bot token

The Inputs section also shows the required WebRequest address: https://api.telegram.org. Add it in MT5 under Tools >> Options >> Expert Advisors >> Allow WebRequest for listed URL.

This is not the same as AI Telegram signal copying. This is EA-side notification logic. For Telegram as a signal source, use: AI Telegram signal copier in AlgoWay.

Wrapped Values

Some alerts may send wrapped values such as:

{
  "platform_name": "metatrader5",
  "order_action": "buy",
  "ticker": "EURUSD",
  "order_contracts": "0.10",
  "stop_loss": "stop_loss=100",
  "take_profit": "take_profit=200",
  "trailing_pips": "trailing_pips=80"
}

Wrapped values should be used only when the current route explicitly supports them. Clean numeric JSON values are easier to debug.

Common Problems and Where to Fix Them

Problem	Likely layer	Guide
AlgoWay does not receive the alert	TradingView webhook / JSON	Webhook Error 415 guide
EA does not receive commands	Webhook UUID / EA connection	MT5 setup guide
MT5 says trading disabled	Algo Trading permission	Error 4752 guide
Order is rejected	Broker execution / request parameters	Error 4756 guide
Wrong symbol	Symbol mapping	Common MT5 errors guide
SL/TP rejected	Stop level, freeze level, points/pips	Risk management guide
Trade opens outside the expected daily time	Daily Window Time Mode does not match the clock used by the user	Check UTC, Broker Time or Local Time, then verify Daily Trade Window
Entry rejected while the market is open	Max spread, session, daily window or position limit	Check the MT5 Experts log for [SPREAD], [SCHEDULE] or [LIMIT]

Safe Testing Procedure

When setting up a new MT5 automation route, test in layers:

1. Confirm that the EA is connected in MT5.
2. Confirm Reverse / Hedge / Opposite / Inverse and Position size: Lots / Risk% / Balance%.
3. Keep Daily Window Time Mode on UTC for an existing configuration, or deliberately select Broker Time or Local Time for a new one.
4. Temporarily use Daily Trade Window 00:00-23:59 and ensure at least one UTC session is enabled.
5. Send a simple market order with a very small valid lot.
6. Check AlgoWay Webhook Logs and MT5 Experts/Journal logs.
7. Test Max spread in points, 0 = disabled with a safe value before enforcing it live.
8. Add exact SL/TP prices, then test distance-based SL/TP.
9. Add trailing stop, breakeven or profit lock one feature at a time.
10. Test close/flat logic and partial close only after full close works correctly.

How to Use This v206 Reference

The URL contains v206 because it was created during an earlier documentation cycle. The content has since been updated to match the current AlgoWayWS-MT5 EA 2.14 workflow while preserving the existing address for users who may still have older links or references.

This reference now covers the main topics required for the current MT5 automation workflow:

• TradingView to MT5 EA;
• MT5 webhook EA;
• TradingView alerts to MetaTrader 5;
• MT5 Expert Advisor JSON fields;
• MT5 EA trailing stop automation;
• MetaTrader 5 WebSocket EA;
• AlgoWayWS-MT5 EA guide.

Related AlgoWay Guides

• How to connect TradingView to MetaTrader 5 with AlgoWay EA
• How to install an MT5 Expert Advisor for AlgoWay automation
• AlgoWay JSON schema guide
• Advanced risk management and trade automation
• How AlgoWay handles opposite trading signals
• MetaTrader 5 common errors in AlgoWay
• How to fix MT5 Error 4752
• How to fix MT5 Error 4756
• How to fix AlgoWay webhook Error 415
• AI Telegram signal copier in AlgoWay

Final Summary

AlgoWayWS-MT5 EA 2.14 is the current MT5 execution component for AlgoWay automation. It receives commands from AlgoWay, executes them in MetaTrader 5, and supports trade modes, lot/risk/balance sizing, order-filling selection, SL/TP controls, trailing, breakeven, profit lock, partial close, symbol mapping, spread and position limits, UTC sessions, selectable Daily Trade Window clocks, Auto-Close, Telegram connection notifications and detailed diagnostics.

If you want to automate TradingView alerts to MetaTrader 5, start with a clean AlgoWay webhook, install the current EA, confirm the WebSocket connection, send valid JSON, test a small market order, and only then enable advanced risk and management features.