How to Copy Trade on TradingView: Webhook Setup Guide

TradingView alerts can send messages to an external execution service, but an alert is not a confirmed broker trade. A webhook workflow requires a supported receiver, correct account permissions and checks at each stage. Copying a person's orders and executing a Pine strategy's signals are different sources of instructions.

Define the Execution Chain

The usual chain is: chart condition → TradingView alert → webhook receiver → broker request → broker acknowledgement and fill. A successful earlier step does not prove a later one succeeded. TradingView's strategy automation documentation does not provide direct automated strategy execution through its broker panel.

Check current plan features for webhook availability and alert limits. The old Pro plan label is not a reliable purchasing guide.

Configure a Receiver Before Enabling Execution

Choose a service that documents support for your exact broker, asset class, account type and order types. Read its message schema, authentication method, retry behavior and position reconciliation rules. Do not select a provider from an unverified millisecond-latency ranking.

Start with a paper or demo connection. For example, TradersPost documents a paper-broker test workflow. That establishes a supported testing path, not a comparative endorsement or a live execution guarantee.

Check whether a terminal or EA must stay running. A cloud service and a locally hosted copier have different availability requirements; a VPS is not universally required and does not guarantee uninterrupted execution.

Use the Receiver's Exact Message Format

The following JSON illustrates field concepts only. It is not a ready-to-send schema for a named provider:

{
  "action": "buy",
  "symbol": "EURUSD",
  "sl": 1.0800,
  "tp": 1.0950,
  "qty": 1
}

Resolve what qty means before sending it: one share, contract, lot and unit are not interchangeable. Confirm whether stop and target fields are prices or distances. Map the chart symbol to the broker instrument, including exchange, expiry and suffix where applicable. Define exits and reversals as well as entries.

Do not put account passwords or unrestricted API keys in alert messages. Use the provider's supported authentication process and minimum required permissions. Keep withdrawal access disabled where separate permissions are available.

Create and Inspect the Alert

1. Configure the chart condition and intended trigger frequency.
2. Create an alert and enable the Webhook URL notification.
3. Enter the receiver's endpoint and its documented message.
4. Confirm TradingView two-factor authentication is enabled.
5. Trigger a controlled test and inspect TradingView's alert log, receiver log and broker order record separately.

TradingView's webhook guide specifies ports 80 or 443, a three-second processing timeout and possible delivery failures. Valid JSON is sent with a JSON content type; webhooks can also carry plain text. These transport details do not imply an order fill within three seconds.

Running alerts use a snapshot of the script and its settings. Recreate an alert when changes need to affect it; see the Pine alerts documentation.

Test Failure Cases and Multiple Accounts

Before live use, test rejected orders, stale messages, duplicates, partial fills, disconnects and an exit arriving when the broker position differs from the expected position. Record identifiers and timestamps for the entire chain. Decide how to stop new instructions and reconcile existing exposure.

For multiple accounts, verify ownership, authorization, quantity scaling, limits and exit handling on each account. Technical support does not override a prop firm's agreement. Apex's agreement, for example, distinguishes permitted copying of manually entered orders from prohibited automated order logic. Do not assume one firm's rules apply to another.

Demo testing can expose configuration errors but cannot prove identical live fills or profitability. Continue monitoring after deployment; ten successful trades are not evidence that a system can be left unattended.

Where Pineify Fits

Pineify can help draft the indicator or strategy conditions used as a signal source. Review generated code and test its realtime behavior. Code generation does not verify the webhook receiver, grant broker permission or guarantee trading results.

FAQ

Does a delivered webhook mean my trade filled? No. Check the broker's order and position records, including rejections and partial fills.

Can I use any copier's JSON example? No. Field names, units and supported actions depend on the receiver.

Which copier is fastest or cheapest? This guide has no reproducible comparative benchmark or current vendor-price audit. Evaluate documented compatibility, total cost and your own end-to-end test results.