Human-written formats
Supported Telegram messages can describe BUY/SELL, market or price-based entries, entry ranges, Stop Loss and one or several Take Profit prices without using a rigid JSON format. AI interpretation happens before order routing.
Turn permitted Telegram channel or group signals into MetaTrader 5 trades without manually retyping entries, stops and targets. AlgoWay interprets supported signal messages, routes a structured instruction to your connected MT5 Expert Advisor and lets you decide how the terminal should manage the position.
AlgoWay routes signals; it does not provide them. The MT5 terminal and Expert Advisor must stay connected.
Telegram and MetaTrader 5 do different jobs. A message like “BUY GOLD, entry range, SL, TP” is not a broker order. AlgoWay first interprets the provider's instruction, then the MT5 bridge applies your account-specific execution rules.
You do not need a second Telegram-specific Expert Advisor. The Telegram Signal Copier is the source connection; AlgoWay WS-MT5 or UB-MT5 is the execution component. The same EA can also be used for other AlgoWay sources, with separate webhook settings.
Supported Telegram messages can describe BUY/SELL, market or price-based entries, entry ranges, Stop Loss and one or several Take Profit prices without using a rigid JSON format. AI interpretation happens before order routing.
Configure a fixed EA lot or select sizing based on the route and EA settings. MT5 can apply lots, risk-percent or balance-percent modes; symbol mapping is maintained separately for your broker.
The EA works with the terminal's symbol specifications, volume increments, position mode and order-filling constraints. Trade filters, sessions, daily loss limits, spread limits, trailing and other EA Inputs remain yours to configure.
Prices in this example are illustrative, not current market quotes. A signal is not a guaranteed fill: a pending entry may never execute, the broker can reject invalid stops, and a position size can be too small for the account's permitted volume step.
Some signal providers give only one target, while others send several. The AlgoWay MT5 EA 2.20 source includes an optional EA-managed Multiple Take Profit feature. It monitors an existing MT5 position and attempts partial closes at independently configured TP1, TP2, TP3 and TP4 distances.
Keep the EA's Multiple TP option disabled and let your Telegram route process the targets supplied by the provider, using its selected execution mode. This is appropriate when you want exits based on the original message.
Enable Multiple TP in EA 2.20 and set your own distances and close percentages. This mode replaces the normal broker Take Profit, including a TP received from the provider; it does not merely fill in absent targets.
| EA stage | Distance from actual entry | Share of initial position to close | Purpose |
|---|---|---|---|
| TP1 | 0.4% | 40% | Reduce exposure at the first favorable move |
| TP2 | 0.8% | 30% | Second partial exit |
| TP3 | 1.2% | 20% | Keep a smaller position for continuation |
| TP4 | 1.6% | 10% | Exit the final scheduled portion |
This example uses MULTI_TP_PERCENT; the distances are price percentages from the actual MT5 entry price, not percentages of account balance. Use MULTI_TP_PIPS when you prefer distances interpreted through the EA's pip-size settings. The allocation percentages refer to the original position volume.
Levels with zero distance are disabled. Enabled distances must increase and assigned close percentages must be positive and total no more than 100%.
For hedging accounts the EA uses ticket-based partial closes; for netting accounts it sends a reducing opposite-side trade. Both approaches remain subject to broker execution rules.
The EA stores initial volume and completed stage markers in MT5 terminal global variables. The running EA is still needed to monitor prices and send later partial closes.
A stage may not result in a close when the calculated volume is below the broker's minimum or increment. The EA rounds down to allowed steps rather than silently increasing the requested partial close. Successful stage execution also depends on live price, connection and broker acceptance.
The order matters: establish the Telegram source, connect the account, validate its symbol and lot rules, then test with a real MT5 demo order before enabling unattended execution.
Create an AlgoWay Telegram Signal Copier connection for a channel or group you are authorized to use. Check source selection and filtering so commentary does not become a trade instruction.
Use the MT5 execution route in AlgoWay. Review signal interpretation settings, sizing and whether Telegram targets are split or the position's exits will be managed inside MT5.
Install the compatible AlgoWay WS-MT5 EA on Windows or UB-MT5 on Ubuntu/Wine. Enter the webhook UUID in the EA Inputs, enable Algo Trading and confirm the terminal is connected.
Map GOLD to the broker's XAUUSD symbol where necessary. Review MT5 minimum lots and steps, volume mode, Stop Loss rules, allowed spread, sessions and any EA-managed TP1–TP4 values.
Send a controlled demo signal, then inspect the AlgoWay log, MT5 Experts and Journal tabs, actual broker fill, Stop Loss and resulting lots. Test a close or partial close before relying on automation.
EA-managed exits require a running, connected MetaTrader 5 terminal. A suitable VPS can keep MT5 available when your personal computer is turned off; no VPS can guarantee network or broker uptime.
Telegram signal setup guide · MT5 EA connection guide · MT5 symbol and lot-sizing guide
EA position-size modes include SIZE_LOTS, SIZE_RISK_PERCENT and SIZE_BALANCE_PERCENT. Risk-percent sizing needs a usable Stop Loss; the actual volume depends on broker symbol properties. Review the result rather than assuming every provider's lot recommendation suits your account.
A Telegram provider may write GOLD, XAUUSD or a broker-specific suffix. AlgoWay supports mapping to the destination symbol. TP distances in pips depend on the EA's pip calculation mode and instrument characteristics; a fixed number of pips is not equivalent across every asset.
EA Inputs support trailing Stop Loss, break-even, profit lock, daily loss limits, maximum drawdown per trade, maximum open positions, sessions and end-of-day/week automatic flattening. Each option has its own trigger and should be tested independently.
Separate a message that was received, a signal that was interpreted, a request that was routed, and an order that was actually filled. MT5 and broker logs are the final evidence of execution, not a Telegram message or HTTP acknowledgment.
Yes. Connect a permitted Telegram source to AlgoWay, route the interpreted instruction to an MT5 destination and keep the compatible AlgoWay MT5 Expert Advisor connected in your terminal.
No. Telegram is handled as a signal source in AlgoWay; the existing AlgoWay WS-MT5 or UB-MT5 EA handles execution on the configured MetaTrader 5 account.
You can use the message's target, configure an appropriate fallback through available settings, or enable EA 2.20's own TP1–TP4 ladder. When EA-managed Multiple TP is enabled, it replaces ordinary broker TP instructions, even when the message already includes a target.
Not by itself. EA-managed Multiple TP watches an existing position and attempts staged partial closures. Telegram-side multi-target execution is a separate mode that may generate multiple entries, so review both configurations.
Yes, the EA 2.20 source exposes an independent close percentage for each TP stage. Distances must be increasing and the total configured close percentage cannot exceed 100%. Broker minimum lot and step rules still apply.
No. EA-managed TP stages are monitored by the running terminal. Without a live EA connection, its local staged exits cannot be processed. The position can still be affected by any broker-side orders that remain active.
AlgoWay has a native WebSocket/TLS Ubuntu/Wine-oriented EA variant alongside the Windows WebSocket build. Choose a compatible build and confirm connection and broker execution in your environment.
Check that EA 2.20 is installed, Multiple TP is enabled, target distance and close percentage are valid, MT5 is online, the position belongs to the configured EA, and the resulting close volume meets the broker's minimum and step rules. Inspect the Experts log and broker result code.
Connect a signal source, configure the MT5 destination and check actual execution before using live funds. Review signal-level target splitting and EA-level Multiple TP as separate decisions.
Related guides: TradingView to MT5 · Telegram Signal Copier · MT5 invalid stops
AlgoWay is a technical order-routing tool. It does not provide trading signals, investment advice or custody of customer funds. Automated trading involves substantial financial risk, including execution errors and missed exits. Broker rules and availability vary by account.