Webhook-driven execution
Alerts fire an HTTP POST with a JSON payload; the copier parses it and places the order — no manual clicking, no custom code to maintain.
Independent guide · Updated for 2026
The TradingView trade copier playbook — from alert to live broker fill
TradingView is where you build strategies and fire signals — but it doesn't place most trades for you. A trade copier bridges that gap, turning your TradingView alerts and webhooks into automated orders on futures, forex, stock and crypto brokers.
- 10+
- Supported brokers & platforms
- <1s
- Typical webhook execution*
- 24/7
- Cloud-based routing
*Execution speed depends on your copier, broker API and network.
TradingView finds the trade. A copier places it.
TradingView is one of the world’s most popular platforms for charting, analysis and building strategies in Pine Script. What it does not do — for the vast majority of brokers — is automatically fire live orders from your strategy alerts. Its native broker integrations are built primarily for manual order placement from the chart.
That leaves a gap between the moment a signal appears and the moment an order actually reaches your broker. A TradingView trade copier fills that gap. When your alert fires, TradingView sends a webhook — a small HTTP message — to the copier, which parses the instruction and submits the corresponding order through your broker’s API. Done well, this happens in well under a second and can fan a single signal out to multiple accounts at once.
In short: TradingView answers “what and when”; the copier handles “execute it, everywhere, now.”
How TradingView webhook automation works
Five stages turn a chart signal into a live order. Understanding each one makes it far easier to build reliable alerts — the exact JSON and broker specifics live in your copier’s setup documentation.
A signal fires on TradingView
Your indicator, drawing, or Pine Script strategy meets its condition and triggers an alert on TradingView’s servers — so it fires even with your browser closed.
The alert sends a webhook
The alert posts a JSON payload to a webhook URL over HTTPS. Placeholders like {{ticker}} and {{strategy.order.action}} inject the live symbol, side and size.
The copier receives & parses it
The bridge accepts the request (ports 80/443 only) and must respond within TradingView’s 3-second window, then translates the payload into a concrete broker order.
Orders route to your broker(s)
The copier authenticates to each broker API and submits the order — optionally to many accounts at once, each scaled by its own multiplier and risk rules.
Risk logic is applied
Attached stop-loss, take-profit and OCO brackets are placed alongside the entry, and reverse/flip logic closes any opposing position first when configured.
Before you automate
What you need to get started
- A paid TradingView plan Webhook alerts require a paid tier (Premium per TradingView’s pricing page). The free Basic plan can’t send webhooks.
- 2-factor authentication TradingView only permits webhook alerts when 2FA is enabled on your account.
- A trade copier / bridge A no-code service or self-hosted endpoint that receives the webhook and talks to your broker’s API.
- A connected broker account Live or funded, on a platform your copier supports (futures, forex, stocks or crypto).
- A well-formed alert payload JSON using placeholders like {{strategy.order.action}} and {{strategy.order.contracts}} to describe each order.
Official constraints
TradingView webhook limits worth knowing
These come straight from TradingView’s webhook documentation. Most “my alert fired but nothing traded” problems trace back to one of them.
- Transport
- HTTPS only — ports 80 and 443 are the only accepted ports.
- Response window
- Your endpoint must reply within 3 seconds or the request is cancelled.
- IPv6
- Not supported — the receiving server must be reachable over IPv4.
- Source IPs
- Requests come from 4 fixed TradingView IPs you can whitelist.
- Rate limit
- Strategy alerts stop if they trigger more than 15 times in 3 minutes.
- No guaranteed retry
- A failed or missed webhook may not be resent — build for reliability.
Where TradingView signals can be executed
Copiers reach brokers through their APIs, so coverage varies by tool. These platforms are commonly supported for futures, forex, equities and crypto — see the broker setup FAQ for connection specifics.
Match-Trader
A trading platform used by a growing number of forex and multi-asset prop firms.
Tradier
An API-first US brokerage often used for equities and options automation.
Binance
A major crypto exchange reachable via API keys for spot and derivatives automation.
Bybit
A crypto derivatives exchange commonly connected for automated futures and perpetuals.
Ironbeam
Coming soonA futures broker listed as an upcoming integration for TradingView automation.
Tastytrade
Coming soonAn options-focused broker listed as an upcoming integration.
Automating prop firm accounts the right way
Most funded-futures programs run on Tradovate, Rithmic or ProjectX — so if your firm uses one of those, TradingView automation is usually within reach. The catch is compliance: automation must respect the rulebook.
Reachable via the platform layer
TradovateCloud futures — most funded futures programs
RithmicLow-latency futures routing used across firms
ProjectXPowers TopstepX and similar prop platforms
Verified supported firms
- Apex Trader FundingRithmic / Tradovate
- TopstepProjectX (TopstepX)
- BulenoxRithmic / Tradovate
- E8 MarketsMulti-platform
A non-exhaustive sample. Firms running these platforms are broadly supported — see the full supported prop firms list.
What a capable trade copier actually does
The strongest tools share the same core toolkit. Here's what to look for — and how each capability shows up in your alert configuration.
Multi-account copying
Route one signal to many broker or funded accounts at once, with per-account quantity multipliers so each account sizes correctly.
Built-in risk controls
Attach stop-loss and take-profit, OCO/bracket orders and percentage- or fixed-quantity position sizing that propagate to every account.
Reverse & flip logic
Close an opposing position before opening a new one, stack same-direction entries, or ignore duplicate signals — controlled from the payload.
Symbol mapping
Alert on one ticker and trade another, and handle broker-specific contract names and futures rollover without rewriting your alerts.
Paper trading & testing
Dry-run the full alert-to-order path on a simulated account before risking capital, then switch the same setup to live.
TradingView trade copier FAQ
The questions traders ask most, answered from TradingView’s own documentation and neutral, firm-agnostic facts.
Not on its own for most brokers. TradingView is a charting and signal platform: it fires alerts when your conditions are met. It offers native "Trading Panel" order placement with 100+ integrated brokers, but that is primarily for manual orders from the chart. To turn strategy alerts into fully automated live orders, you connect a trade copier or webhook bridge that receives the alert and submits the order to your broker’s API.
Still have questions? Browse the full automation FAQ for broker- and payload-specific details.
Put it into practice
Ready to turn your TradingView alerts into automated broker fills?
You’ve got the concepts — the pipeline, the brokers, the prop-firm caveats. The next step is a hands-on setup: connect a broker, generate a webhook, and paste it into your alert. These step-by-step guides walk through exactly that.
Educational resource only — not financial advice. Automated trading carries risk; test on a simulated account first and confirm your prop firm’s rules before going live.