TradingView webhook to MT5 — signals you review, or opt-in auto-trade

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.

Each alert carries a small JSON message with the instrument, direction, entry, stop-loss and take-profit. TradingView POSTs it to your private PipSync URL, PipSync validates it, and a valid alert appears as a signal on the Signals page for you to review. To let alerts trade, set up auto-trade under Settings → Advanced → TradingView Alerts with an explicit consent, then link your accounts and switch it on under Accounts & auto-trade. The same webhook handles single price alerts and strategy alerts.

1. 1

   Create your PipSync account and subscribe to a plan

   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 (payment method required, cancel any time). It covers everything required to wire up and test the TradingView webhook before you go live.

2. 2

   Generate your webhook URL

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

3. 3

   Connect your MT5 account

   Open Trading Accounts → Add account and choose MetaTrader 5, using your master (trading) password. 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. Use real stop-loss and take-profit prices — an alert with 0 is rejected — and add no size field such as lots: an alert that names its own size is never auto-traded. 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

   Fire a test alert before going live

   Fire the alert once, then open Settings → Advanced → TradingView Alerts and check Recent alerts: each call is listed with its status and, if it was rejected, the exact error. A valid alert shows up on the Signals page. Use an MT5 demo account while you test.

7. 7

   Optional: switch on auto-trade

   Once a few alerts have parsed as expected, tick the consent under Settings → Advanced → TradingView Alerts and click Set up auto-trading (Advanced plan). Then open Accounts & auto-trade, link your MT5 account and switch auto-trade on. Until you do, every alert stays a signal for your approval.

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 five required fields: instrument, direction, entry, sl and tp1. direction is buy or sell (long and short also work); instrument is the chart symbol, for example {{ticker}} — PipSync upper-cases it and keeps only letters and digits, and there is no symbol-mapping setting, so if your broker spells it differently, message the support chat.

entry, sl and tp1 must be prices above 0 — 0 is rejected, not read as market (use tp1 to tp5 for several targets). comment is ignored. A size field never sets the size: an alert that names its own size or risk (for example lots, qty, contracts, size, volume, units, amount or risk) is not auto-traded and is saved as a signal for your approval. 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. Only JSON alerts can auto-trade; a plain-text alert is always saved as a signal for your approval.

• instrument — required: the chart symbol, for example {{ticker}}
• direction — required: buy or sell (long and short also work)
• 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; there is no close action
• lots, qty, contracts, size, volume, units, amount or risk — never used for sizing; an alert carrying one is not auto-traded

Entries yes, exits no. 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, with your levels as entry, sl and tp1. Each valid alert becomes a signal for you to review, or, with auto-trade on, is placed when it passes every check.

PipSync does not close positions from TradingView alerts: a direction other than buy or sell is rejected. While a position in the same instrument opened by a TradingView alert is still open, a new alert for that instrument is not traded, in either direction; an opposite-direction alert is held as a likely strategy exit and saved as a signal for your approval. Exits happen by the stop loss, the take profit, or by you in PipSync and your broker platform.

Only if you opt in. Auto-trade is off by default and needs the Advanced plan: under Settings → Advanced → TradingView Alerts you give an explicit consent and click Set up auto-trading, then under Accounts & auto-trade you link your MT5 account and switch auto-trade on. Without that, every alert stays a signal for your approval.

With auto-trade on, the loss at the stop loss is capped at the channel risk, 0.5% of the account balance by default. If the risk cannot be measured on an account (the balance is unknown, there is no contract data, or the account is not held in USD for now — for now, auto-trade values the risk only for currency pairs: gold, indices, crypto and other CFDs on MT5, cTrader and Match-Trader accounts are not traded), or the broker's smallest lot would exceed the cap, that account is not traded. If every account was refused by these limits, the alert is kept as a signal for your approval; if the broker rejects the order on every account, the signal is marked rejected. Slippage and price gaps can make the actual loss larger than the cap. If the de-duplication service is unavailable, alerts are only saved as signals. An alert is traded automatically only when all of these hold:

• it is a JSON alert — plain-text alerts are always saved as a signal for your approval
• it comes from TradingView's published sender IP addresses
• it names no size of its own (for example lots, qty, contracts, size, volume, units, amount or risk) — otherwise it is a signal for your approval
• your Advanced plan is still active
• it is not a duplicate — TradingView retries are de-duplicated
• your workspace is under 5 automatic executions per minute
• no position in the same instrument opened by a TradingView alert is still open, in either direction

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.

PipSync's webhook integration needs a plan that includes it (the Advanced plan).

TradingView POSTs your JSON to the PipSync webhook URL, PipSync parses and validates it, and a valid alert is saved as a signal named TradingView Alert on the Signals page, scored like any other signal. Invalid alerts are answered with HTTP 422 and the reason is listed under Recent alerts.

Unless you have switched on auto-trade, PipSync does not open the trade itself — open the signal on the Signals page to review it; when you confirm it, sizing follows your settings (fixed lots or percent-risk, min/max lots, max open positions). With auto-trade on, an alert that passes every check is placed on your linked accounts with the loss at the stop loss capped at the channel risk; one that does not is saved as a signal for your approval. Because all of this runs in the cloud, the pipeline keeps working when your computer is off — there is no VPS to babysit.

Fire the alert once, then open Settings → Advanced → TradingView Alerts and look at Recent alerts, which lists the last 20 alerts received on your URL with their status and, if one was rejected, the exact error. A valid alert shows up on the Signals page.

For the first real alerts, use an MT5 demo account and keep auto-trade off, so every alert stays a signal you review. Switch to your live account, or switch on auto-trade, only after a few alerts have parsed exactly as expected.