TradingView Futures Automation

From a Futures Strategy to an Executable Order

Start with one complete instruction: the market, account environment, contract, direction, number of contracts and protection. A chart label such as NQ identifies the market family. It does not settle the expiry or the symbol expected by an execution API.

The alert also needs the right event. A simulated limit fill is not the same as a request to place a working limit order at the broker. The Pine Script guide explains why a strategy's historical trades and a live order workflow need separate interpretation.

Continuous Symbols and Dated Contracts

Chart symbol

A continuous symbol such as NQ1! represents a rolling chart series. TradingView documents manual trading of eligible 1! continuous futures through its own interface, with orders directed to the current front contract. That platform behavior does not establish how an external webhook receiver handles the same text. ^[S07]

Execution symbol

A receiver may accept a continuous alias, perform a documented mapping or require a dated contract identifier. TradersPost documents continuous-contract handling in its futures guide; AlgoWay and PickMyTrade routes need their own destination-specific checks. Do not infer one service's mapping behavior from another service's example. ^{[S17] [S20] [S22]}

For a route requiring a dated symbol, choose the current tradable contract from the destination's instrument list. Copy its exact syntax. This guide deliberately does not embed a supposedly permanent “current NQ contract”: that value changes.

Rollover ownership

Record who updates the execution mapping. A chart rolling to a new underlying contract does not necessarily update a fixed ticker in an alert body. A running alert also retains its created context. Review the alert, mapping and open orders as separate objects during rollover. ^{[S04] [S08]}

Tradovate, Rithmic, ProjectX and Broker Routes

These names identify different execution environments, not interchangeable credentials. Confirm the supported connection with the service and the account provider.

The table is a connection checklist, not a claim that AlgoWay supports every row. Compare AlgoWay with TradersPost and PickMyTrade using their documented routes, then verify the exact account environment. ^{[S17] [S20] [S22]}

A prop account adds a permission question beyond technical compatibility. Read the prop firm guide before connecting an automated route.

Ticks, Points, Contracts and Bracket Orders

A point is a price distance; a tick is an instrument's minimum price increment. For an illustrative contract with a 0.25 tick size, a 10-point distance equals 40 ticks. The calculation says nothing about currency risk until the contract's point value and quantity are known.

Do not substitute a micro contract for a larger contract while leaving all assumptions implicit. Verify the instrument specification and intended exposure. A strategy trading one contract should produce one executable contract in its entry test, with no conversion to lots or currency notional.

A bracket workflow must establish three outcomes: entry acceptance, stop acceptance and target acceptance. After an exit, inspect remaining working orders. A closed position with an orphaned order is not the same as a flat account with no future exposure.

The Tradovate community has a dedicated question about cancelling remaining bracket orders. It is a useful test scenario, not proof that every connector leaves orders behind. Verify cancellation in the route you actually use. ^[R10]

Rollover, Session Boundaries and Prop Accounts

Build a simple operating record for the strategy: contract mapping, session timezone, permitted holding window and the location of protection. Check scheduled session boundaries independently of the chart's displayed timezone.

A webhook close command and cancellation of pending orders are distinct operations. Test what the chosen route actually does when flattening. A future entry order can remain working even though the current position is flat.

Use the execution guide for missed or late instructions and the webhook guide for message delivery. Do not change contract mapping to repair a transport failure.

Questions and Answers

Can I send NQ1! directly to my execution platform?

Only when the receiver documents that alias and maps it appropriately. TradingView's manual continuous-contract support is not a universal webhook translation rule.

Who updates the contract at rollover?

The responsible component depends on the route. Record whether the service resolves an alias or you maintain a dated symbol, then verify it at rollover.

Does a successful entry guarantee that my stop was placed?

No. Inspect the accepted stop and covered quantity separately. Also check what remains after a target or manual exit.

Is a futures CFD equivalent to an exchange-traded futures contract?

No. Read the destination instrument specification. A similar chart name does not establish the same contract, trading hours or account infrastructure.