TradingView to MT4 — webhook alerts executed without a VPS

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.

The traditional workaround is a Windows VPS running MT4 plus a bridge EA that polls a third-party relay — three moving parts that all have to stay up. With PipSync the webhook terminates in the cloud and the trade is placed from there, so your alert keeps executing even when your computer and your charts are closed. You stay in control: the alert can carry its own price, stop-loss, take-profit and lot size, or leave sizing to your server-side risk rules.

1. 1

   Create a PipSync account and connect MT4

   Sign up at app.pipsync.io — the free plan is enough to build and test this route. Add your MetaTrader 4 account as the broker connection; starting with a demo account is recommended.

2. 2

   Get your PipSync webhook URL

   In the dashboard, go to Sources → Add Source → TradingView Webhook. PipSync generates a unique URL containing a secret token. Copy it and treat it like a password — anyone who has it can send signals to your account, and you can regenerate it from the Sources page if it is ever exposed.

3. 3

   Create the alert in TradingView

   Open the Alerts panel (the clock icon, or Alt+A) and set the condition: either order fills from a Pine strategy, or a simple condition such as a price level or indicator cross. Webhook notifications are a paid TradingView feature — the free TradingView plan cannot send them.

4. 4

   Paste the JSON into the alert message

   In the Message field, use PipSync's template: {"action": "{{strategy.order.action}}", "symbol": "{{ticker}}", "price": {{close}}, "sl": 0, "tp": 0, "lots": 0.01}. For a simple alert, replace the action placeholder with a hardcoded "buy" or "sell", and replace sl, tp and lots with fixed values or strategy variables as needed.

5. 5

   Add the webhook URL and save

   Under Notifications, tick Webhook URL, paste your PipSync URL and click Create. From now on, every time the alert fires, TradingView POSTs the JSON to PipSync, which validates it and routes the order to your MT4 account.

6. 6

   Test before going live

   Use Send Test Signal on your TradingView source in PipSync to fire a sample payload and inspect the parsed result and the broker's response. Keep the route on a demo account — optionally with Manual Approval mode on — until you have watched a few real alerts execute exactly as expected.

Typical setup time: about 12 minutes.

Because MT4 is a desktop terminal with no inbound web endpoint: TradingView delivers alerts by POSTing JSON to a URL, and there is simply nothing in MetaTrader 4 that can listen for that request. The platforms speak different languages — push HTTP on one side, a closed terminal on the other.

The classic workaround chains together a third-party relay service, a Windows VPS, and a bridge EA running inside MT4 that polls the relay for new alerts. It works, but you pay for the VPS, you maintain the EA, and the whole chain stops the moment the terminal crashes, Windows updates, or the relay subscription lapses.

PipSync removes the terminal from the receiving path entirely. The webhook terminates on PipSync's servers, the payload is validated there, and the order is executed on your MT4 account server-side. There is no relay to subscribe to, no EA to attach to a chart, and no machine of yours that has to stay on.

PipSync expects a small JSON object in the alert's Message field — two required fields and a few optional ones. TradingView replaces double-brace placeholders with live values when the alert fires, so one message template can serve every trigger.

One MT4-specific caveat: the symbol field must match your broker's instrument name exactly as it appears in the symbol list. Many MT4 brokers add suffixes or use their own naming, so if {{ticker}} doesn't match what your broker calls the instrument, hardcode the broker's symbol in the message instead of using the placeholder.

• action (required): "buy", "sell" or "close" — "close" closes the open position on that symbol
• symbol (required): the instrument name exactly as your broker lists it (e.g. XAUUSD, US30, EURUSD)
• price (optional): entry price; 0 means execute at current market price
• sl / tp (optional): stop-loss and take-profit prices; 0 means none
• lots (optional): overrides your risk rules for this trade — omit it to let your configured server-side sizing decide
• comment (optional): a trade comment, useful for telling strategies apart in your MT4 history

Use a strategy alert if your logic lives in a Pine strategy() script, and a simple alert for one-off conditions — both can POST to the same PipSync webhook. The difference is what the placeholders can resolve.

A strategy alert fires on the strategy's order fills, so a single alert covers both entries and exits: {{strategy.order.action}} resolves to "buy" or "sell" depending on which order just filled, and the same message template handles both directions.

A simple alert — a price crossing a level, an indicator condition — has no strategy context, so {{strategy.order.action}} stays empty and the payload would be rejected. For simple alerts, hardcode the action ("buy" in one alert, "sell" in another) and create one alert per direction. Price and symbol placeholders like {{close}} and {{ticker}} work in both alert types.

No — that is the point of this route. The webhook is received, validated and turned into an order on PipSync's servers, and the trade is executed on your MT4 account server-side. There is no EA to install, no chart that must stay open, and no Windows VPS to rent and patch.

MT4 support is live in PipSync's public beta and covers what MT4 traders expect: hedging accounts work, and stop-loss and take-profit are placed server-side with the order rather than managed by a fragile client-side script. Every received webhook and every resulting order is logged in the dashboard, so you can audit exactly what TradingView sent and what your broker filled.

You decide, per route, whether the alert or your server-side rules control sizing. If the alert includes a lots value, that exact size is used for the trade; if you omit it, PipSync applies the risk rules you configured — and those rules run on the server, before any order reaches MT4.

For exits you have the same choice: put sl and tp prices in the alert payload, or send a follow-up alert with action "close" to flatten the position on that symbol. While you are still validating a strategy, Manual Approval mode holds each incoming signal for your confirmation instead of executing it immediately — combined with a demo account, that lets you watch the full TradingView → MT4 chain end to end with nothing at stake.