TradingView to MT4 — coming soon, without a VPS

Risk warning: Trading CFDs and other leveraged products is complex and carries a high risk of losing money rapidly because of leverage. Industry data indicates that 70–80% of retail trading accounts lose money on these products. Risk disclosure · Past performance.

Not available yet: this destination cannot be connected in PipSync today. MetaTrader 5, cTrader, Match-Trader, Binance and Bybit are live; we will update this page when it opens.

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 signal is created there, so your alerts keep arriving even when your computer and your charts are closed. You stay in control: the alert carries its own entry, stop-loss and take-profit, and each resulting signal waits for your review on the Signals page.

1. 1

   Create a PipSync account (MT4 coming soon)

   Sign up at app.pipsync.io (the $0 Free plan needs no card but only parses signals), then subscribe to a plan that includes webhook integration — enough to build and test this route. MT4 account connections are coming soon; until then you can already set up the webhook and review alerts as signals.

2. 2

   Get your PipSync webhook URL

   In the dashboard, go to Settings → Advanced → TradingView Alerts and click Generate webhook URL. PipSync generates a unique URL containing a secret token and shows it only once. Copy it and treat it like a password — anyone who has it can send signals into your workspace and, once auto-trade is on, trigger trades. Regenerate it on the same screen if you suspect a leak.

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: {"instrument": "{{ticker}}", "direction": "{{strategy.order.action}}", "entry": {{close}}, "sl": 0.0000, "tp1": 0.0000}. Replace both 0.0000 values with real prices — an alert with 0 is rejected. For a simple alert, replace the direction placeholder with a hardcoded "buy" or "sell". Add no size field such as lots: an alert that names its own size is saved as a signal for your approval.

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 saves it as a signal on the Signals page.

6. 6

   Test before going live

   Fire the alert once, then open Settings → Advanced → TradingView Alerts and check Recent alerts for its status and any error. Keep testing on a demo account until you have watched a few real alerts parse 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 a valid alert becomes a signal. 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 — five required fields. TradingView replaces double-brace placeholders with live values when the alert fires, so one message template can serve every trigger.

One MT4-specific caveat: many MT4 brokers add suffixes or use their own naming. There is no symbol-mapping setting for alerts, so if your broker's naming differs from {{ticker}}, message us in the support chat with the symbol and your broker.

Plain-text alerts are always saved as a signal for your approval, and only JSON alerts can ever be traded automatically.

• instrument (required): the chart symbol, e.g. {{ticker}}
• direction (required): buy or sell (long and short also work) — there is no close action
• entry (required): entry price, above 0
• sl (required): stop-loss price, above 0
• tp1 (required): at least one take-profit price, above 0
• comment: ignored
• lots, qty, contracts, size, volume, units, amount or risk: never used for sizing; an alert carrying one is saved as a signal for your approval

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 {{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 a signal on PipSync's servers. There is no EA to install, no chart that must stay open, and no Windows VPS to rent and patch.

MT4 account connections are coming soon in PipSync. Every received webhook is listed under Recent alerts in the dashboard, so you can audit exactly what TradingView sent and how PipSync read it.

Each valid alert becomes a signal on the Signals page, where you review it, and by default PipSync places no order from it. Sizing follows your settings (fixed lots or percent-risk, min/max lots, max open positions); an alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk) is saved as a signal for your approval.

For exits, put sl and tp prices in the alert payload: PipSync does not close positions from TradingView alerts, so exits happen by stop loss, take profit or by you. While you are still validating a strategy, review every signal by hand and test on a demo account, so you can watch the TradingView chain end to end with nothing at stake.

Not on MT4: MT4 account connections are coming soon, so on this route every alert is a signal you review. Elsewhere in PipSync, auto-trade from TradingView is opt-in and off by default; it needs the Advanced plan and is set up under Settings → Advanced → TradingView Alerts with an explicit consent.

Only JSON alerts from TradingView's published sender addresses that name no size of their own can ever be traded automatically; a plain-text alert, or an alert that names its own size, is always saved as a signal for your approval.