Why MetaTrader has no inbound webhook (and how to automate TradingView alerts anyway)

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. Risk disclosure · Past performance.

This guide explains the technical reason MetaTrader has no inbound webhook, walks through the two classic workarounds — a listener EA on your own machine and a Windows VPS running a bridge EA — including where they fail, and then shows the cloud-routing setup that removes terminal-side infrastructure entirely.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io — no credit card needed. Everything this guide covers, from generating your webhook URL to firing test signals at a demo account, works on the free plan.

2. 2

   Add a TradingView webhook source

   In the dashboard, go to Sources → Add Source → TradingView Webhook. PipSync generates a unique webhook URL for your account (pipsync.io/api/tradingview/webhook/<your-secret-token>). Treat it like a password: anyone with the URL can send signals to your account, and you can regenerate it from the Sources page if it is ever exposed.

3. 3

   Connect your MT5 account

   Add your MetaTrader 5 account as the destination and set your server-side risk rules — lot sizing, SL/TP mapping, max open trades, symbol filters. Starting on a demo account is recommended.

4. 4

   Create the TradingView alert

   In TradingView, create an alert on your strategy or condition. In the Message field, paste the JSON payload PipSync expects — action, symbol, price, sl, tp, lots — using placeholders such as {{strategy.order.action}}, {{ticker}} and {{close}} so TradingView fills the values when the alert fires. Then, under Notifications, enable Webhook URL and paste your PipSync URL.

5. 5

   Send a test signal and go live deliberately

   In PipSync, open Sources → your TradingView source → Send Test Signal to see the parsed result and whether the broker accepted it without waiting for a real alert. Keep Manual Approval mode on and stay on demo until a few alerts have executed exactly the way you expect.

Typical setup time: about 12 minutes.

A webhook is an HTTP callback: when an event happens in one system, that system sends an HTTP POST request — usually with a JSON body — to a URL that another system has published in order to receive it. The defining property is direction: the receiver does not poll for updates; it exposes a public endpoint and waits to be called.

TradingView alerts work exactly this way. When an alert fires, TradingView POSTs the alert message once, immediately, to whatever webhook URL you entered in the alert's notification settings. So the whole question of "MetaTrader webhooks" reduces to one question: is there a URL on the internet that leads to your MT4/MT5 terminal? There is not — and the next section explains why that is structural, not a missing setting.

Because the MetaTrader terminal is a desktop client, not a server. It runs on your PC behind your router's NAT and firewall, it has no public IP, no domain, no TLS certificate — and, most fundamentally, MetaQuotes ships no inbound HTTP listener in the terminal at all. There is no option to switch on and no port to open inside the terminal; the capability does not exist in the product.

What MQL4/MQL5 do offer is outbound networking. An Expert Advisor can call WebRequest() to poll an external server for new signals (after you allowlist the URL under Tools → Options → Expert Advisors), and it can open raw sockets. With enough work an EA can even host a listener on a local port of your machine. But a local listener is still not a webhook endpoint: TradingView, out on the public internet, cannot reach a process behind your home router.

Architecture matters here too. Orders are accepted by your broker's MetaTrader server; the terminal is only the client that submits them. Any automation therefore has to either drive a running terminal (the EA approach) or talk to the broker through an API bridge — which is exactly what cloud routing services do.

Technically yes; practically it is the most fragile option available. The pattern: an EA or helper program listens on a local port, you configure port forwarding on your router so the internet can reach that port, and you give TradingView your home IP (or a dynamic-DNS name) as the webhook URL.

Each link in that chain is a failure mode you now own:

• Your home IP changes — most residential connections rotate addresses, so the webhook URL silently goes stale unless you maintain dynamic DNS.
• Port forwarding exposes your trading PC — you are publishing an open port to the entire internet, typically without proper TLS or authentication hardening.
• Everything must stay up at once — the PC, the terminal, the EA on its chart, the router config and your connection; a Windows update or a closed chart breaks the route without warning.
• Missed alerts are simply lost — if your endpoint is down when the alert fires, there is no queue waiting for your machine to come back.

A VPS moves the problem rather than removing it. The standard recipe is a Windows VPS running a MetaTrader terminal plus a third-party bridge EA; a small web service receives the TradingView webhook and the EA places the trade inside the terminal. This does work — it is what most "TradingView to MT5" tools sold today actually are under the hood.

The costs are recurring and operational rather than one-off:

• Monthly VPS rent on top of whatever the bridge tool itself costs.
• The terminal must stay logged in 24/7 with the EA attached to a chart — terminal auto-updates, broker re-login prompts and VPS reboots all stop execution silently.
• You become a Windows server administrator: patching, RDP security, disk space, monitoring.
• Risk logic lives in EA input fields on one machine; nothing validates an order server-side before it reaches your broker.

By giving TradingView a webhook URL that points at a service which already runs server-side and already speaks to your broker. With PipSync, you copy a unique per-account webhook URL from the dashboard (Sources → Add Source → TradingView Webhook), paste it into the alert's Webhook URL field, and put a small JSON payload in the alert message.

When the alert fires, PipSync's servers receive the POST, parse the payload, apply your server-side risk rules — lot sizing, SL/TP mapping, max open trades, symbol filters — and route the order to your MetaTrader account through an API bridge. No terminal-side EA, no open port at home, no Windows server to maintain, and execution continues when your computer is off. Because the webhook terminates at PipSync rather than at a terminal plugin, the destination is interchangeable: the identical alert can execute on MT4, MT5, cTrader, Match-Trader, Binance Futures or Bybit without changing anything on the TradingView side.

PipSync is in public beta and is an execution tool: it routes the alerts you create, it does not generate signals, and nothing on this page is investment advice.