TradingView Prop Firm Trading: Alerts, Webhooks and Pine

Option 1: Trade from the chart with a broker integration

Some firms integrate with TradingView as a broker, so you can click to trade on the chart. This is the most familiar experience but depends on the firm being an official TradingView broker partner.

Option 2: Alerts to a webhook

TradingView alerts can send a JSON message to a webhook URL. A prop firm that accepts webhooks turns that message into an order on your account. This works for indicators, drawings and Pine strategies, and it runs while your computer is off.

On QATS every account gets a personal webhook URL. Messages carry the symbol, side, size and optional protective orders; an alert log shows what was received and what was executed or rejected, and why.

Help CenterTradingView and QATS step-by-step

Option 3: A trading ticket on top of TradingView

A browser extension can add an order ticket to the TradingView page itself. QATS Trade for Chrome does this: you see your QATS account, positions and risk limits beside the chart and place orders without switching tabs.

Help CenterConnect QATS Trade for Chrome

Pine strategies: what to watch

• Use “once per bar close” alerts for strategies to avoid repainting signals.
• Send explicit position size in the message rather than relying on defaults.
• Attach a stop loss; the prop firm’s daily loss limit still applies to automated orders.
• Test the full loop on a sandbox before connecting a paid evaluation.

Writing alert messages that execute cleanly

A webhook order is only as good as the message behind it. Use explicit fields — symbol, side, quantity or notional, and an order type — rather than free text. Keep one alert per action: an entry alert and a separate exit alert are easier to audit than one alert that tries to infer what to do from the current position.

Use TradingView placeholders such as {{ticker}} and {{strategy.order.action}} in Pine strategy alerts so the order always matches the signal that fired, and include a client reference so you can match each alert to a fill in the alert log.

Common webhook mistakes

• Alerts set to fire “once per bar” on a strategy that repaints, producing signals that disappear on the closed bar.
• Symbols that do not match the prop account’s instrument names (for example BTCUSD vs BTCUSDT).
• Expired alerts — TradingView alerts can have an expiry date; check it after editing.
• Sizing in the message that ignores the account’s leverage and position limits, so orders are rejected.
• Testing on a paid evaluation instead of a sandbox first.

Risk rules still apply

Automation does not change the evaluation. On QATS, webhook orders pass the same server-side checks as manual ones — a 10% profit target, a 4% daily loss limit, a 6% end-of-day trailing maximum loss that stops trailing at the starting balance, a 40% consistency rule and 2 minimum trading days. An order that would break leverage or position limits is rejected and logged.