May 21, 2026

TradingView Alerts to a Futures Trade Copier: What to Include

How to design TradingView webhook alerts for futures copying, including external IDs, actions, quantities, and continuous contract symbols.

Send a stable external ID

A webhook needs a stable identifier for the source event. Without one, duplicate alerts can become duplicate orders. Use an order ID, alert ID, strategy order ID, or another deterministic value that stays the same if the alert retries.

Keep actions explicit

The copier should receive clear actions such as buy or sell, plus quantity and symbol. Avoid ambiguous text like enter now or close maybe. The engine can only protect users when the message shape is predictable.

Handle continuous contracts

Many traders chart symbols like NQ1! or ES1!. A copier should normalize continuous chart symbols to the correct tradable root and contract route, then apply broker-specific mapping before sending follower orders.

Test before scaling

Start with a paper or evaluation account and confirm that entries, exits, partial fills, and reversals behave as expected. Webhooks are powerful, but a bad alert template can send the wrong instruction very quickly.