Video learning: Complete Premium V2 framework tutorial · Historical Pionex automation overview (legacy interface; not a V2-specific setup guide).
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.
Start here
This guide is written for users who can operate TradingView but may have never automated a strategy before. You do not need to understand Pine Script. The key is to choose the correct integration route, create the correct TradingView alert, and verify the full chain with a demo or minimum-size trade before using normal size.
The one rule to remember For TradeSmart-built PineConnector, TradersPost, or Custom Template automation, create a strategy alert using Order fills only and use {{strategy.order.alert_message}} as the TradingView alert Message. |
|---|
The 3 routes
| Route | Use it when | TradingView Message |
|---|---|---|
| A. Provider-Native | The service generates its own TradingView JSON/text payload (common with 3Commas, WunderTrading and many hosted bots). | Use the exact provider-generated payload. |
| B. Verified Adapter | You select PineConnector Verified Adapter or TradersPost Verified Adapter inside the TradeSmart script. | {{strategy.order.alert_message}} |
| C. Custom Templates | Your webhook service/private server has its own documented command format. | {{strategy.order.alert_message}} |
Fastest safe setup
- Load the strategy. Use the correct chart symbol, timeframe and preset/settings.
- Verify Strategy Tester. Make sure the strategy behaves as expected before automation.
- Configure Automation. Turn Use Automation ON, choose the integration route and keep Automation Safe Mode ON for initial testing.
- Create the alert. Use Order fills only. Use the provider payload or
{{strategy.order.alert_message}}as required by your route. - Add the webhook URL. Paste the exact URL supplied by your provider.
- Test small. Prove long entry, short entry, exits, quantity and symbol mapping before normal size.
- Recreate alerts after changes. TradingView alerts keep a snapshot of the script, symbol, timeframe and inputs at creation time.
| Important Changing a strategy input on the chart does not update an already-running TradingView alert. If an execution-relevant setting or script version changes, delete/recreate the alert. |
|---|
1. How TradeSmart Automation Works
A TradeSmart strategy does not directly log into your exchange or broker. TradingView runs the strategy, its broker emulator fills strategy orders, and a TradingView alert sends a webhook message to an execution service. That service then sends a real order to the connected broker or exchange.
| Step | What happens |
|---|---|
| 1 | The V2 strategy detects an entry, exit, DCA, add-on or other order event. |
| 2 | TradingView’s strategy engine fills the simulated strategy order according to its broker-emulator rules. |
| 3 | The order-fill alert fires in real time. |
| 4 | TradingView sends the alert Message to the webhook URL. |
| 5 | The provider parses the message and decides what real broker/exchange action to request. |
| 6 | The broker/exchange accepts, rejects or fills the live order under real market conditions. |
| Why Order fills only? TradeSmart automation is designed around strategy order fills. A plotted signal or an alert() call can occur at order submission time, while an order-fill alert is tied to the strategy emulator’s execution event. For execution automation, the fill event is the cleaner reference point. |
|---|
Fill alerts are not pending-order placement alerts
This matters for strategies that use stop or limit orders. For example, Wickless retest entries and ORB breakout logic can create orders that sit inside TradingView’s broker emulator. The external provider normally receives the webhook when TradingView says the strategy order filled. Unless you intentionally use a provider-specific pending-order workflow, the real broker did not necessarily have an identical pending order waiting in advance.
-
Fast price movement can therefore create live slippage relative to the Strategy Tester.
-
A live provider can reject an order because of minimum size, precision, margin, broker rules or symbol mapping.
-
A historical backtest fill does not produce a webhook. Strategy alerts trigger on real-time executions only.
-
More than one fill can legitimately occur on the same bar.
2. Before You Connect Anything
TradingView prerequisites
-
Enable two-factor authentication (2FA) on TradingView before using webhook alerts.
-
Use a TradingView plan that supports webhooks.
-
Confirm the V2 strategy is loaded on the exact symbol and timeframe you intend to automate.
-
Set strategy capital, order size/risk, commission and slippage deliberately; do not leave them misunderstood.
-
Keep the TradingView alert log visible during first tests.
Provider prerequisites
-
Connect only the intended broker/exchange account.
-
Use paper/demo trading where available for the first complete test.
-
Confirm whether the account is netting or hedging.
-
Confirm how the provider interprets quantity: shares, contracts, base units, quote currency, lots, percentage or provider-side sizing.
-
Confirm the exact broker symbol. EURUSD, EURUSD.a, BTCUSDT, BTC/USDT and BTCUSDT.P can be different instruments to different systems.
| Do not copy secrets into Pine Never place exchange API secrets, broker passwords, wallet keys or private credentials in Pine inputs or public alert examples. Use the provider’s secure account connection and authentication system. |
|---|
3. Universal V2 Automation Settings
The synchronized V2 framework uses the same core automation controls across the current premium strategies. The group number in the Inputs panel can differ by strategy, but the meaning is the same.
| Setting | Beginner default | What it does |
|---|---|---|
| Use Automation | ON when automating | Enables TradeSmart-generated automation payloads and automation safety logic. Provider-Native alerts are a special case: an already-created provider-native alert can still send its own message even if this input is later turned off. |
| Automation Integration | Choose your route | Provider-Native TradingView Payload, PineConnector Verified Adapter, TradersPost Verified Adapter, or Custom Manual Templates. |
| Automation Safe Mode? | ON | Uses conservative common-denominator behavior where supported, including close-first reversal handling and safer overlap behavior. |
| Automation Flip Handling | Close First Then Wait For Next Signal | Safer starting mode. One-Step Reversal should only be enabled after the provider/account behavior is proven. |
| Order Comment Mode | Readable Order Labels | Keeps Strategy Tester order comments readable. Automation Payload is mainly diagnostic. |
| PineConnector License / Custom Routing ID | Blank unless needed | PineConnector uses this as the License ID. Custom templates can access it as {provider_id}. |
| Adapter / Custom Symbol Override | Blank initially | Overrides the chart ticker for PineConnector, TradersPost or custom messages when the broker/provider uses a different symbol. |
| Adapter / Custom Quantity Multiplier | 1.0 initially | Scales adapter quantities. Particularly important when converting TradingView quantity into MetaTrader lots. |
| PineConnector / Custom Extra Parameters | Blank initially | Adds optional PineConnector parameters or exposes {provider_extra} to custom templates. |
Safe Mode
Safe Mode is the recommended first-live configuration because different providers handle overlapping positions and opposite orders differently. An opposite order can reverse, flatten, partially reduce, or open a hedge depending on the service and account mode.
| Beginner default Safe Mode ON + Close First Then Wait For Next Signal + no overlap/pyramiding until basic parity is proven. |
|---|
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.