Before you begin: Start with the Smart Trader onboarding checklist and the V2 automation overview. Never use a live account until you have confirmed symbol, order quantity, all intended entry/exit types and risk settings with a demo or minimum-size test.
12. First-Time Testing Protocol
Do not test everything at once. The purpose is to isolate one failure mode at a time.
| Test | Pass condition |
|---|---|
| 1. Long entry | Correct symbol, side and quantity at provider and broker. |
| 2. Short entry | Correct symbol, side and quantity. |
| 3. Full exit / stop | Closes/reduces the intended position; does not accidentally open the opposite side. |
| 4. Final TP | Closes the intended remaining quantity. |
| 5. Partial TP | Only the expected quantity is removed; remainder is correct. |
| 6. DCA | Adds in the same direction at the intended size. |
| 7. Add-On | Adds in the intended direction and does not replace/flip unexpectedly. |
| 8. Flip | First validate close-first. Test one-step reversal separately if you plan to use it. |
| 9. Overlap/pyramiding | Aggregate live exposure matches strategy intent. |
| 10. Alert snapshot | After changing an input, recreate the alert and verify the new alert uses the new settings. |
Compare four records
-
TradingView Strategy Tester / chart order markers
-
TradingView Alerts Log and Webhook status
-
Provider signal/bot logs
-
Broker/exchange order and fill history
For each test record timestamp, order ID/reason, side, symbol, requested quantity, executed quantity and price. A webhook being marked ‘sent’ is not the same as a broker fill.
13. Emergency Stop and Troubleshooting
Emergency stop procedure
-
Pause/delete the TradingView alert immediately.
-
Stop/disable the provider bot or webhook route.
-
Inspect real broker/exchange positions and pending orders.
-
Flatten/cancel manually if needed.
-
Save the TradingView alert log and provider log before changing settings.
-
Compare timestamp, event/reason, side, symbol, quantity and position state.
-
Do not reactivate until the exact failure is understood and reproduced safely.
| Symptom | Likely cause | Check |
|---|---|---|
| Provider receives nothing | Wrong webhook, alert condition, expired/stopped alert | TradingView alert status, Webhook status, URL, 2FA, alert expiration |
| TV alert fires; broker does nothing | Provider rejected message or broker rejected order | Provider log, auth/routing, symbol, quantity, market status |
| Wrong quantity | Unit conversion/multiplier | TradingView qty vs broker units/lots and provider sizing rules |
| Wrong symbol | Ticker mapping mismatch | Chart ticker, provider ticker, broker suffix/prefix |
| Exit opens opposite trade | Provider close semantics mismatch | Reduce/exit/reversal/account mode |
| Partial closes full position | Provider does not honor requested partial size | Partial syntax, minimum lot, rounding |
| Flip ends flat | Opposite order only flattened | Use close-first or configure tested reverse semantics |
| Long and short both remain open | Hedge-mode behavior | Broker/account/provider position mode |
| Live alert differs from chart | Old frozen alert snapshot | Delete/recreate after input/source/symbol/timeframe change |
| Many messages same bar | Legitimate multiple fills, DCA, OCO, partials | Order IDs/reasons in alert log |
| Alert suddenly stops | Too many triggers or expiration/error | Alert status; TradingView limit of >15 triggers in 3 minutes |
| Webhook errors | Receiver timeout/HTTP rejection | Webhook status, provider uptime, payload validity |
14. Security and Webhook Reliability
-
TradingView currently requires 2FA for webhook alerts.
-
TradingView sends webhook alerts as HTTP POST requests.
-
If the alert body is valid JSON, TradingView sends application/json; otherwise it uses text/plain.
-
TradingView documents support for ports 80 and 443 only for webhook URLs with explicit ports.
-
TradingView documents a roughly 3-second processing timeout for the remote server.
-
TradingView notes that webhooks can occasionally fail; check the Webhook status column in the alert log.
-
Do not include passwords, broker logins, wallet keys or exchange API secrets in alert bodies.
-
Use HTTPS and the provider’s official webhook endpoint.
| Automation is a chain TradingView can correctly generate a fill event while the real trade still differs because the provider, broker, market liquidity or connection behaves differently. Automation reduces manual action; it does not remove execution risk. |
|---|
15. Future V2 Strategy Compatibility
This guide is intended to remain valid for upcoming V2 framework strategies that retain the synchronized automation architecture. Before treating a new script as compatible, verify these items:
-
It is a TradingView strategy, not only an indicator.
-
It includes the V2 Automation group with the same four integration choices.
-
It attaches alert_message values to all order-producing events that should be automated.
-
It uses the strategy order-fill default message
{{strategy.order.alert_message}}. -
It preserves Safe Mode / flip handling semantics or documents any intentional exception.
-
Any new event type (for example, a new staged exit) has a defined automation message path.
| Version changes Whenever a V2 Pine source is updated, recreate the live TradingView alert after loading the new version. A running alert continues using the old server-side snapshot. |
|---|
16. Official Documentation References
Provider interfaces can change. These references were checked while preparing this edition; always compare the guide with the provider’s current documentation before live deployment.
TradingView - Alerts FAQ: https://www.tradingview.com/pine-script-docs/faq/alerts/
TradingView - Strategy Alerts: https://www.tradingview.com/support/solutions/43000481368-strategy-alerts/
TradingView - Alerts on alert() function: https://www.tradingview.com/support/solutions/43000597494-alerts-on-alert-function/
TradingView - Webhook configuration: https://www.tradingview.com/support/solutions/43000529348-how-to-configure-webhook-alerts/
TradingView - Variable/placeholders in alerts: https://www.tradingview.com/support/solutions/43000531021-how-to-use-a-variable-value-in-alert/
3Commas - Signal Bot JSON guide: https://help.3commas.io/en/articles/16281112-signal-bot-comprehensive-json-guide
WunderTrading - TradingView automated trading: https://wundertrading.com/en/tradingview-automated-trading
WunderTrading - Signal Bot: https://wundertrading.com/en/signal-bot
PineConnector - Syntax: https://docs.pineconnector.com/syntax
PineConnector - Add alerts to your script: https://docs.pineconnector.com/low-code
TradersPost - Signal Message Reference: https://docs.traderspost.io/docs/core-concepts/webhooks
TradersPost - TradingView integration: https://docs.traderspost.io/docs/learn/signal-sources/tradingview
Scope and responsibility
This is an integration and operational guide, not financial advice. Strategy backtests and TradingView broker-emulator fills are not guarantees of live fills or profitability. Use demo/paper trading and conservative size until the complete alert-provider-broker chain has been validated for the exact instrument and account.
One-page quick reference
| If you use… | V2 Integration | TradingView Condition | TradingView Message |
|---|---|---|---|
| 3Commas / WunderTrading / provider-generated bot JSON | Provider-Native TradingView Payload | Order fills only | Exact provider-generated message |
| PineConnector | PineConnector Verified Adapter | Order fills only | {{strategy.order.alert_message}} |
| TradersPost | TradersPost Verified Adapter | Order fills only | {{strategy.order.alert_message}} |
| Private server / unsupported provider | Custom Manual Templates | Order fills only | {{strategy.order.alert_message}} |
-
Default first test: Safe Mode ON, close-first flip, no overlap, no DCA/add-ons, no partial TP.
-
Recreate alert after any relevant script/input/symbol/timeframe change.
-
Do not trust quantity until you have verified one minimum-size real/demo order end-to-end.
-
Provider-Native emergency stop: pause/delete TradingView alert and/or stop provider bot.
Based on the TradeSmart V2 Premium Universal Automation Guide, September 2026 edition. Provider interfaces can change; compare provider instructions before real-money deployment. This guide describes V2 framework strategies, not every legacy V1 integration.
Download the complete TradeSmart V2 Automation Guide
Download the complete September 2026 universal guide (DOCX). This is the complete source handbook covering all providers and safety checks.