TradingView webhook to MT5 — execute alerts automatically

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.

Each alert carries a small JSON message with the action, symbol and optional price levels. TradingView POSTs it to your private PipSync URL, PipSync validates it against your server-side risk rules, and the order lands on your MT5 account. The same webhook handles single price alerts and full strategy automation with separate entry and exit alerts.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io — no credit card needed. The free plan covers everything required to wire up and test the TradingView webhook before you commit to anything.

2. 2

   Generate your webhook URL

   In the dashboard, go to Sources → Add Source → TradingView Webhook. PipSync creates a unique URL with a secret token. Copy it and treat it like a password — anyone holding it could send signals to your account, and you can regenerate it any time.

3. 3

   Connect your MT5 account

   Add a broker account and choose MetaTrader 5. PipSync executes server-side, so there is no EA to install and your terminal does not need to stay open. Start with a demo account.

4. 4

   Create a TradingView alert with a JSON message

   In TradingView, open the alert dialog (Alt+A), set your condition, and paste PipSync's JSON template into the Message field. Placeholders such as {{ticker}}, {{close}} and {{strategy.order.action}} are filled in by TradingView when the alert fires.

5. 5

   Paste the webhook URL into the alert

   In the same dialog, scroll to Notifications → Webhook URL and paste your PipSync URL, then click Create. From now on, every time this alert triggers, TradingView POSTs the JSON to PipSync.

6. 6

   Send a test signal before going live

   In PipSync, open your TradingView source and use Send Test Signal to fire a sample payload without waiting for a real alert. Check the parsed result and the broker response on a demo account, and consider Manual Approval mode for your first live alerts.

Typical setup time: about 12 minutes.

Because a webhook needs a server that listens for incoming HTTP requests, and the MT5 terminal is a desktop application with no inbound endpoint. TradingView can only POST an alert to a public URL — there is nothing in MetaTrader 5 for it to call.

The traditional workaround is to rent a Windows VPS, keep an MT5 terminal running on it 24/7, and install an EA plus a local bridge that receives the webhook and relays it to the terminal. That stack is fragile and entirely yours to maintain. PipSync replaces it: the webhook endpoint, the parsing and the order routing all run on PipSync's servers, and orders are sent to MT5 through its API bridge. If you want the deeper background on why MetaTrader has no native webhook support, the MetaTrader webhook guide linked below covers MT4 and MT5 in detail.

A small object with two required fields — action and symbol — plus optional price levels. action is "buy", "sell" or "close"; symbol must match the instrument name exactly as it appears in your broker's MT5 symbol list (for example XAUUSD, US30 or EURUSD).

The optional fields are price (0 means execute at market), sl and tp (0 means none), lots (a fixed size that overrides your configured risk rules for that one trade — omit it to let PipSync size the position) and comment (a free-text trade comment). TradingView placeholders make the message dynamic: {{ticker}} inserts the chart symbol, {{close}} the current price, and {{strategy.order.action}} the direction of a strategy order.

• action — required: "buy", "sell" or "close"
• symbol — required: the MT5 instrument name from your broker's symbol list
• price — optional: entry price; 0 = market execution
• sl / tp — optional: stop-loss and take-profit prices; 0 = omit
• lots — optional: fixed size that overrides your risk rules; omit to use them
• comment — optional: free-text trade comment visible in MT5

Yes — the route is built for it. Set your alert condition to the strategy's order fills and use {{strategy.order.action}} in the JSON so the same alert sends "buy" when your strategy goes long and "sell" when it goes short. Entries and reversals then flow through one alert.

For explicit exits, create a second alert whose message uses the action "close": it closes the open position on that symbol on your MT5 account. This entry-plus-exit pattern means your Pine Script strategy can run a complete cycle — open, manage, flat — without you touching the terminal.

Yes. Webhook notifications are a paid TradingView feature — TradingView's free plan can show alerts on screen but cannot POST them to a URL. This is a TradingView limitation, not a PipSync one.

On the PipSync side a free plan exists (€0, no credit card required to start), so the TradingView subscription is the only paid prerequisite for testing this route end to end.

TradingView POSTs your JSON to the PipSync webhook URL, PipSync parses and validates it, applies your server-side risk rules, and routes the order to your MT5 account. Every step is logged, so you can open the dashboard afterwards and see what was received, how it was interpreted and what your broker answered.

Risk rules sit between the alert and the order: if you omit lots, PipSync sizes the position from your configured rules (fixed lots or percent-risk), and guardrails such as maximum open trades or symbol filters apply before anything reaches the broker. Because all of this runs in the cloud, the pipeline keeps working when your computer is off — there is no VPS to babysit.

Use the built-in test signal: in PipSync, open your TradingView source and click Send Test Signal. It pushes a sample payload through the full pipeline and shows you the parsed result and whether the broker accepted the order — no waiting for a live alert to fire.

For the first real alerts, point the route at an MT5 demo account and optionally enable Manual Approval mode, which holds each trade for your confirmation before execution. Switch to your live account only after a few alerts have parsed and executed exactly as expected.