How to connect TradingView to MT5 without code.

Before you connect TradingView to MT5

A bridge sends instructions from a TradingView alert to an Expert Advisor running inside MetaTrader 5. This guide covers that direction: TradingView to MT5. It does not add your MT5 account to TradingView's broker trading panel.

• A TradingView account with webhook alerts available and two-factor authentication enabled.
• An MT5 demo account with trading enabled. Check the exact symbol name, minimum lot size and whether its market is open.
• A SignalForge account and the webhook URL shown in your dashboard.
• A running MT5 terminal with the SignalForge EA connected, on your computer or on SFCloud.

TradingView explains the webhook and 2FA requirements in its official setup guide. Keep broker passwords out of alert messages. Treat your personal webhook URL as a secret.

Choose local MT5 or hosted MT5

Local: run MT5 on your own computer with the EA attached and automated trading enabled. Keep the computer awake and connected. The bridge subscription does not keep a switched-off terminal running.

SFCloud: use a managed MT5 terminal that runs independently of your computer. Connect your broker account through the SFCloud setup flow. Hosting needs the account credentials requested by that flow; never paste them into a TradingView alert.

Starter bridge is $4.99/month; Starter + SFCloud is $9.99/month. Standalone SFCloud at $6.99/month does not include the bridge. The 14-day no-card trial applies to the Starter and Trader bridge plans; cloud bundles are paid from day one. TradingView is separate. See current plans and inclusions.

Connect TradingView to MT5 in four steps

1. Add your demo account. Check the broker server and MT5 login in SignalForge. Copy the webhook URL from your dashboard rather than typing a URL from an example.
2. Connect the EA. For local MT5, follow Setup to install the current EA, enable automated trading and add the required WebRequest address. Confirm its connection status before proceeding. With SFCloud, complete the hosted terminal setup and check that the account and EA are connected.
3. Create the TradingView alert. Choose the intended indicator or strategy condition. In Notifications, enable Webhook URL and paste your personal URL. Set the trigger frequency and expiration deliberately.
4. Add the message and verify a triggered order. Use the dashboard's alert builder for your demo account, symbol and execution settings. Saving an alert is not proof of execution: its condition must trigger, and the resulting order must be checked in MT5.

A minimal alert message

{"action":"buy","symbol":"EURUSD","lot":0.01,"account":"YOUR_DEMO_LOGIN"}

This is a template, not a ready-to-send trade. Replace YOUR_DEMO_LOGIN with the intended MT5 login and EURUSD with the broker's exact symbol. Check the account's sizing settings: risk-based sizing can change the effective volume. This example does not define SL/TP; configure the intended stops and their units before testing. A broker may reject 0.01 lots for some instruments.

Targeting account avoids an accidental broadcast to other connected accounts. Use the webhook guide for the full message setup. Do not copy TradingView contracts directly into MT5 lots without checking contract units.

Confirm each stage of the first demo order

1. TradingView: find the triggered alert and check its Webhook status.
2. SignalForge: find the corresponding signal. Check the target account and whether it was executed, filtered or rejected.
3. MT5: verify the order or deal, direction, symbol, volume and stops. A received webhook alone does not prove a broker fill.

After inspecting the result, manage or close the demo position in MT5. Do not repeat the alert blindly when a result is unclear: first check whether the original order exists.

TradingView alert fired, but MT5 did not trade

• No alert in TradingView: check the condition, timeframe, frequency and expiration.
• Alert fired, delivery failed: check Webhook status, the URL and 2FA. Follow TradingView's delivery error details.
• Signal received, EA disconnected: check the terminal, broker login, network, automated trading and WebRequest setup.
• Connected but rejected: read the rejection reason. Check symbol spelling, trading session, minimum volume, margin and account filters.
• Wrong volume or stops: compare message fields with the account's execution mode. Price levels, pips and lot sizes are not interchangeable.

Use the documentation for configuration and support with the signal time and error text. Remove tokens and passwords from screenshots or copied logs.

Common connection questions

Can I connect TradingView to MT5 for free?

You can try the SignalForge bridge for 14 days without a card. TradingView webhook access and any hosted MT5 service have separate requirements and costs.

Does MT5 need to stay open?

Yes. The terminal and EA must run somewhere. Local setup needs your computer running; SFCloud runs the terminal remotely.

Does the bridge guarantee the same price as my chart?

No. Alert delivery, terminal availability, broker execution and market prices all affect the outcome. Check real demo fills rather than assuming a latency or fill price.

Can I reuse PineConnector alerts?

SignalForge v4 supports a subset of PineConnector-style commands. Check lot sizing, pending-entry units and account routing before migration; syntax support is not complete feature parity. See the migration checklist.

Choosing a service first? Read the MT5 bridge comparison. This guide focuses on setup and verification.