# TradingView to Match-Trader — signals you review, or opt-in auto-trade

Source: https://pipsync.io/en/tradingview-to-match-trader
Last updated: 2026-06-07

To use TradingView alerts with a Match-Trader account, point your alert's webhook at PipSync: it receives the JSON payload and saves it as a signal on the Signals page for you to review — no VPS, no plugin, nothing installed in the platform. By default PipSync places no order from an alert; auto-trade is opt-in and off by default on the Advanced plan. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there. Telegram and Discord signals execute on Match-Trader as well.

The TradingView-bridge ecosystem grew up around MetaTrader, which leaves traders on Match-Trader — the backend a growing number of prop firms white-label — without a clean way to automate. PipSync connects to Match-Trader directly through its REST and WebSocket interfaces; a TradingView alert becomes a signal you review or, if you opt in on the Advanced plan, is placed automatically on your linked accounts when it passes every check.

## TradingView → Match-Trader at a glance

| | |
|---|---|
| Signal source | TradingView webhook alerts — from indicators, price alerts or Pine Script strategies (webhooks require a paid TradingView plan) |
| Destination platform | Match-Trader (Match-Trade) via REST + WebSocket — live in PipSync |
| Payload format | JSON: instrument, direction (buy/sell), entry, sl and tp1 — all required, sl/tp above 0; TradingView placeholders such as {{ticker}} and {{close}} fill values dynamically |
| Position sizing | An alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk) is never auto-traded; with auto-trade on, the loss at the stop loss is capped at the channel risk (0.5% of the account balance by default); slippage and price gaps can exceed it |
| Auto-trade | Opt-in and off by default (Advanced plan); on Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there |
| Prop guardrails | Apply to Telegram and Discord signals; for TradingView auto-trade the loss at the stop loss is capped at the channel risk, and your firm's own limits stay your responsibility |
| Infrastructure | Fully cloud-based — no VPS, no EA, no Match-Trader plugin |
| Price | Webhook integration needs a plan that includes it (the Advanced plan) |

## How do I connect TradingView to Match-Trader?

You configure the PipSync side once, then every TradingView alert that uses your webhook URL becomes a signal for you to review.

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). It covers the webhook URL and the Recent alerts list.
2. **Generate your TradingView webhook URL** — In the dashboard, go to Settings → Advanced → TradingView Alerts and click Generate webhook URL. PipSync generates a unique webhook URL containing a secret token and shows it only once. Treat it like a password — anyone who has it can send signals into your workspace and, once auto-trade is on, trigger trades — and regenerate it on the same screen if you suspect a leak.
3. **Connect your Match-Trader account** — Open Trading Accounts → Add account and choose Match-Trader; start with a demo or evaluation account. Telegram and Discord signals execute on it; TradingView auto-trade is covered in the last step.
4. **Know what the alert becomes** — Each valid alert becomes a signal on the Signals page for you to review, and by default PipSync places no order from it. Only JSON alerts can auto-trade; a plain-text alert is always saved as a signal for your approval, and so is an alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk).
5. **Create the TradingView alert** — In TradingView (a paid plan is required for webhook notifications), open the Alerts panel, set your condition, and paste the JSON template into the message field — instrument, direction, entry, sl and tp1, with real prices (not 0) for sl and tp1. Placeholders like {{ticker}}, {{close}} and {{strategy.order.action}} fill in the symbol, price and direction at fire time. Then paste your PipSync URL under Notifications → Webhook URL and save. Add no size field such as lots or qty: an alert that names its own size is never auto-traded.
6. **Fire a test alert** — Fire the alert once, then open Settings → Advanced → TradingView Alerts and check Recent alerts: each call is listed with its status and, if rejected, the exact error. A valid alert shows up on the Signals page. Check a few alerts until they behave exactly as expected.
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 accounts and switch auto-trade on. Until you do, every alert stays a signal for your approval. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there.

## Why do so few tools support TradingView alerts on Match-Trader?

Because most TradingView-to-broker bridges were built around MetaTrader: they forward the webhook into an Expert Advisor running inside an MT4/MT5 terminal, so any platform that cannot run MQL EAs never made their list. Match-Trader has no EA mechanism, so it stayed unsupported even as prop firms adopted it as a white-label backend.

PipSync does not depend on a terminal-side component at all. For Telegram and Discord signals, orders reach Match-Trader through a direct REST and WebSocket integration running in the cloud, and a TradingView alert is a signal you review unless you opt in to auto-trade.

## What does a TradingView alert become?

The alert's message field carries a small JSON payload, and TradingView POSTs it to your unique PipSync webhook URL when the alert fires. The payload names the instrument, a direction (buy or sell), an entry price, a stop-loss and a take-profit — all required, and a price of 0 is rejected. There is no close action.

TradingView placeholders make the payload dynamic: {{ticker}} fills in the chart symbol, {{close}} the price at trigger time, and {{strategy.order.action}} the direction your Pine Script strategy decided. PipSync validates the payload and saves it as a signal on the Signals page for you to review. With auto-trade on, an alert that passes every check is placed on your linked accounts instead; on Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there.

Because you author the JSON yourself, there is little parsing ambiguity: what your strategy fires is what lands in the signal, and a malformed alert is rejected with a reason you can read under Recent alerts.

## Can TradingView alerts place trades on Match-Trader automatically?

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 accounts and switch auto-trade on. Without that, every alert stays a signal for your approval. On Match-Trader accounts, too, the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there.

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

## Are automated TradingView strategies allowed on prop-firm accounts?

It depends entirely on the firm, and you must verify before going live. Prop firms differ widely on automation: some permit personal automated strategies, some restrict third-party copy trading, some require pre-approval for any EA-style execution, and the rules can differ between evaluation and funded stages — or change over time.

A TradingView strategy you built yourself is your own trading logic rather than a copied third-party feed, which is how many firms frame the distinction. But the only answer that counts is the one in your firm's current terms or from its support team. PipSync executes what you configure — TradingView auto-trade included; complying with your firm's rules remains your responsibility.

## Does the alert set my position size?

Prop accounts typically enforce daily and overall drawdown limits, and a lots value hardcoded into a TradingView alert would ignore your account balance and the stop distance of the specific trade.

That is why an alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk) is never auto-traded and is saved as 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. Slippage and price gaps can make the actual loss larger than the cap. For Telegram and Discord signals executed on Match-Trader, PipSync computes the lot size server-side from your sizing settings.

Whatever you do, you remain responsible for monitoring the account against your firm's specific limits.

## How is this different from copying Telegram signals to Match-Trader?

The destination is the same; the source could hardly be more different. A TradingView alert is structured JSON generated by your own indicators or Pine Script strategy — deterministic, and fired by TradingView's servers whenever the chart condition is met. A Telegram signal is a human-written message from a third-party provider, which PipSync has to parse with AI because every provider formats differently.

Practically, a TradingView alert gives you ownership of the entry logic and produces a signal you review (or an automatic trade if you opt in), while the Telegram route executes a feed someone else produces, with server-side sizing, min/max lots and max open positions. If your signals come from a Telegram channel rather than your own charts, the telegram-to-match-trader guide covers that route.

## FAQ

### Do I need a paid TradingView plan to send webhook alerts?

Yes. TradingView only offers webhook notifications on its paid plans; the free TradingView plan cannot call a webhook URL. PipSync's webhook integration needs a plan that includes it (the Advanced plan).

### Can a TradingView alert close a position on Match-Trader?

No. PipSync does not close positions from TradingView alerts, and a direction other than buy or sell is rejected: exits happen by stop loss, take profit or by you. An opposite-direction alert while a position opened by a TradingView alert is still open is held as a signal for your approval.

### Should I set the lot size in TradingView or in PipSync?

In PipSync, not in the alert. An alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk) is never auto-traded and is saved as 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. Slippage and price gaps can make the actual loss larger than the cap. For Telegram and Discord signals PipSync applies your server-side sizing.

### Can TradingView alerts auto-trade on Match-Trader?

Only if you opt in: auto-trade is off by default, needs the Advanced plan and is set up under Settings → Advanced → TradingView Alerts with an explicit consent. On Match-Trader accounts the risk of indices, gold or crypto cannot be measured for now, so such alerts are not auto-traded there.

### Does PipSync work with Match-Trader prop-firm accounts?

PipSync can connect a Match-Trader account for Telegram and Discord signals, including prop-firm evaluation and funded accounts — Match-Trader is a common white-label backend among prop firms. Whether automated execution is permitted is a separate question that each firm answers differently, so check your firm's rules before enabling live trading.

### What happens if my PipSync webhook URL is exposed?

Anyone who has the URL can send signals into your workspace and, with auto-trade on, trigger trades, so keep it secret. If you suspect a leak, regenerate it under Settings → Advanced → TradingView Alerts in PipSync and update your TradingView alerts with the new URL; the old one stops working immediately.

### Do I need a VPS to run TradingView alerts into Match-Trader 24/7?

No. TradingView fires the alert from its own servers and PipSync receives and validates it in the cloud, so the webhook runs while your computer is off. There is no terminal, EA or VPS anywhere in the chain.

### Is PipSync a signal provider or a strategy vendor?

No. PipSync is execution infrastructure: it turns alerts you create from your own TradingView setup into signals you review, or automatic trades if you opt in, on your own accounts. It does not sell signals or strategies, does not promise any trading results, and is not investment advice. Trading leveraged products involves substantial risk of loss.

## Related

- [Webhook to Match-Trader — send JSON signals for prop accounts](https://pipsync.io/en/webhook-to-match-trader)
- [Match-Trader copier — route Telegram and Discord signals to Match-Trader](https://pipsync.io/en/match-trader-copier)
- [Telegram to Match-Trader — copy signals automatically](https://pipsync.io/en/telegram-to-match-trader)
- [TradingView webhook to MT5 — signals you review, or opt-in auto-trade](https://pipsync.io/en/tradingview-to-mt5)
- [TradingView to cTrader — signals you review, or opt-in auto-trade](https://pipsync.io/en/tradingview-to-ctrader)
- [Prop firm signal copier — one source, every account](https://pipsync.io/en/prop-firm-signal-copier)
- [Server-side risk management — trading rules enforced before your broker](https://pipsync.io/en/server-side-risk-management)
- [Signal copier with no VPS — execution runs in the cloud](https://pipsync.io/en/signal-copier-no-vps)

---

PipSync is a signal execution tool. It does not provide trading signals, does not guarantee any trading results and is not investment advice. Trading leveraged products involves substantial risk of loss.