Send One TradingView Alert to Multiple NinjaTrader Accounts
You built one TradingView alert. You do not want to repeat the order across every NinjaTrader account by hand. You also do not want to discover after a live signal that the alert reached the source account but one follower missed the stop.
This tutorial builds the smallest testable workflow:
- TradingView sends one webhook alert.
- CrossTrade validates and routes the command.
- The CrossTrade XT Add-On submits the supported action to a NinjaTrader 8 source account.
- A configured CrossTrade copier sends the supported order or execution activity to mapped follower accounts.
- You verify the complete lifecycle in simulation before using a live account.
Before you start
You need:
- An active CrossTrade plan with webhook and Trade Copier access
- NinjaTrader 8 installed and connected
- The current CrossTrade XT Add-On installed and connected
- One simulation source account
- At least one simulation follower account
- A TradingView plan that supports webhook alerts
- Permission to use automation and copying under every applicable broker or prop-firm rule
NinjaTrader 8 and the CrossTrade add-on must remain running for this NT8 workflow. If you need a path with no local NT8 installation, review Tradovate cloud webhook automation.
Understand where copying begins
The webhook does not submit one order independently to every follower. It submits the supported command to the source account you selected. The copier observes the configured source activity and applies your copy rules to the followers.
That separation matters when troubleshooting:
- If the source never receives the order, inspect the TradingView alert, webhook payload, account name, and add-on connection.
- If the source receives the order but a follower does not, inspect copier mapping, copy mode, filters, sizing, and follower state.
Read TradingView and manual trading with the copier for the product model.
Step 1: Connect NinjaTrader 8
- Install or update the CrossTrade XT Add-On.
- Sign in with the intended CrossTrade user.
- Confirm the add-on reports a connected state.
- Confirm the simulation source and follower accounts are visible.
- Stop if an unexpected account is present or a required account is missing.
Use the installation and connection documentation if the add-on is not connected.
Step 2: Create the smallest copier
Open the CrossTrade Trade Copier and create one copier group.
Set:
- One simulation source account
- One simulation follower account
- A simple one-to-one quantity rule
- No inversion
- No instrument replacement unless the test specifically requires it
- No unrelated follower accounts
Starting small makes a mismatch easier to isolate.
Open the Trade Copier configuration guide.
Step 3: Choose the copy mode
CrossTrade supports order and execution copy modes. The right choice depends on what you need the follower to mirror.
- Order mode focuses on order lifecycle replication.
- Execution mode reacts to fills and prioritizes follower execution from the source fill event.
Do not choose based on the word "faster" alone. Test the exact entry, stop, target, change, cancel, and partial-fill behavior your strategy uses.
Step 4: Create the TradingView webhook alert
Use the CrossTrade webhook automation guide to create a valid alert for the simulation source account.
The payload must use the exact account and instrument format expected by the current webhook documentation. Do not copy an old payload from a forum post without checking it.
Before enabling the alert:
- Confirm the source account is a simulation account.
- Confirm quantity is the smallest useful test size.
- Confirm the instrument contract is current.
- Confirm any stop and target values match the documented command format.
- Confirm the alert fires once per intended TradingView condition.
Step 5: Run the first end-to-end test
Trigger one alert and verify in this order:
- The TradingView alert log shows the alert fired.
- CrossTrade signal history shows the request and outcome.
- The source account shows the expected order or execution.
- The follower account shows the copied action.
- Source and follower quantities match the configured ratio.
- Stops and targets exist where expected.
- A cancel or flatten action produces the expected result on both accounts.
Do not proceed because the entry alone worked. The protective and closing actions are part of the test.
Step 6: Test failure recovery
While still in simulation:
- Confirm both accounts are flat.
- Create another test order.
- Interrupt the relevant connection in a controlled way.
- Restore the connection.
- Review source and follower positions, working orders, and copier status.
- Use the documented recovery process if the accounts are out of sync.
Read connection resilience and Trade Copier troubleshooting before performing the test.
Step 7: Expand one variable at a time
After the one-source, one-follower test passes, add only one change per test:
- A second follower
- A different quantity ratio
- Instrument replacement
- Inversion
- A different order type
- A strategy-specific filter
Keep a short record of the configuration and result. If a test fails, roll back the last change.
Troubleshooting map
The source account did not trade
Check:
- TradingView alert history
- Webhook payload syntax
- Account and instrument identifiers
- CrossTrade signal history
- NT8 and add-on connection state
- Trade windows and account controls
The source traded but a follower did not
Check:
- Copier enabled state
- Source and follower mapping
- Copy mode
- Quantity and instrument rules
- Follower connection and account state
- Rejection or block reason in copier logs
The accounts disagree after reconnecting
Stop new automation. Compare positions and working orders. Follow the documented reconciliation process before resuming.
Use NinjaTrader Trade Copier diagnostics for a guided investigation.
Pre-live checklist
Do not use a live or funded account until all of these are true:
- Entry tested
- Stop tested
- Target tested
- Change tested
- Cancel tested
- Flatten tested
- Quantity ratio tested
- Instrument mapping tested
- Reconnect tested
- Logs captured for one full lifecycle
- Current broker and prop-firm rules reviewed
- Rollback plan written