How to connect TradingView to Cloud MT5

1. Before you begin

Have an AlgoWay account, a supported MetaTrader 5 broker account with its login, password and exact broker server name, and a TradingView strategy or indicator capable of producing webhook alerts. Test in a demo broker account before using live funds.

2. Create a Cloud MT5 connection

1. Open Trade Webhooks

   In the AlgoWay Store, choose TradingView under Source — From, and Cloud MT5 under Destination — To. Select a trial where eligible or purchase the Cloud MT5 webhook.

2. Enter the broker server

   In the connection form, type the exact MT5 broker server name (for example, the server shown by your MT5 account). Click Find Broker Server and wait for verification before continuing.

3. Enter MT5 credentials

   Supply the broker account's numeric login and password, and confirm the verified broker server. This is your MT5 broker login — not your AlgoWay account password.

4. Finish the webhook setup

   Review News Filter and Prevent Duplicate Alerts as needed, then create the webhook. You can later edit the connection from the dashboard.

News Filter and duplicate-alert protection

The connection form includes a News Filter selector and a separate Prevent Duplicate Alerts switch. Duplicate protection defaults to off; its window defaults to 10 seconds. When enabled, the configured window skips identical BUY/SELL alerts. Close and modify alerts are unaffected by that window.

3. Start Cloud MT5 and confirm readiness

Open Workspace → Cloud MT5. The dashboard lists each connection, its trial or subscription expiry, MT5 status, EA status and terminal controls.

1. Click Start MT5 (play icon) for the correct connection.
2. Allow the terminal to prepare, authenticate with the broker and connect the EA.
3. Confirm both MT5 and EA indicators are green and the status reads Ready.
4. Use Copy URL for the webhook URL that will go into TradingView.
5. Use Positions, Instruments and History to inspect the broker account.

Use the gear icon for Automation Settings and the pencil icon to edit the webhook/connection details.

4. Configure your TradingView webhook alert

Create an alert on the intended TradingView strategy or indicator. In TradingView's notification settings, enable the Webhook URL option and paste the URL copied with Copy URL from your Cloud MT5 connection. In the Message field, use JSON appropriate for your strategy and configured sizing.

Strategy alert example

{
  "platform_name": "cloudmt5",
  "ticker": "{{ticker}}",
  "order_action": "{{strategy.order.action}}",
  "order_contracts": "{{strategy.order.contracts}}"
}

The double-curly TradingView placeholders are replaced by TradingView when an alert fires. Common actions include buy and sell; make sure your actual strategy action values match the webhook's supported handling. For a non-strategy alert, replace the placeholders with values produced by that alert. Never use a placeholder that your chosen alert type does not provide.

Example fixed-size demo alert

{
  "platform_name": "cloudmt5",
  "ticker": "EURUSD",
  "order_action": "buy",
  "order_contracts": "0.01"
}

After the test, verify the webhook activity, MT5 Positions and History, and Experts log. A successful webhook delivery does not by itself guarantee broker execution.

5. Cloud MT5 Automation Settings — complete reference

Click the gear icon for your Cloud MT5 connection. The Automation Settings screen contains nine sections and 75 fields, matching the Cloud MT5 EA 2.21 settings schema. The defaults below are for new connections; saved settings can differ.

Trade execution

Core routing and broker order interpretation. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Position size & partial closes

Entry lots, scaling and close instructions. Values shown below are the schema defaults, not recommendations for every broker or strategy.

Position sizing: a webhook size of 0.10 lots multiplied by 2 gives 0.20 lots before broker rounding. Risk-based sizing needs valid entry and stop information. Confirm your broker's permitted volume step.

Trailing, break-even & profit protection

Protecting open trades through the EA. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Stop loss & take profit

Override or ignore stop instructions. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Multiple take-profit levels

Up to four partial exits. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Risk controls

Exposure, execution limits and optional progression. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Trading hours & scheduling

Session filters, windows, reset and automatic flat. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Symbol mapping

Broker-specific instrument aliases. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

Telegram alerts & diagnostics

Saved notification preferences and debug option. Values shown below are the schema defaults, not recommendations for every broker or strategy.

These settings are stored per Cloud MT5 connection. Enable a switch only when you want the EA to apply its related controls.

6. Monitoring, logs and diagnosing trade execution

The Cloud MT5 dashboard gives you two separate read-only diagnostic panes. Select the required connection in Cloud MT5 Debug Logs, then use Refresh or allow the interface to update automatically approximately every 6 seconds.

7. Frequently asked questions

Next step: test a complete entry and exit

Start with a demo account, verify an entry, then verify an intentional exit and the final position state. Once symbols, volumes and broker-specific restrictions are confirmed, enable additional EA management features deliberately.

For product details and billing, see Cloud MT5 automation overview. For the unrelated local-terminal installation workflow, use the dedicated MetaTrader 5 EA documentation rather than installing another EA for Cloud MT5.