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.
5. Provider-Native Setup
Choose Provider-Native TradingView Payload when the automation service generates its own account-specific or bot-specific TradingView message. The provider owns the message schema; TradeSmart should not guess or rewrite private IDs, bot UUIDs or service-specific fields.
Generic procedure
-
Create/connect the provider bot or strategy.
-
Select TradingView strategy/webhook as the signal source.
-
Configure the intended exchange/broker account and pair.
-
Copy the provider’s webhook URL.
-
Copy the provider’s exact strategy message/JSON.
-
In the V2 script, set Use Automation ON and Automation Integration = Provider-Native TradingView Payload so Safe Mode/flip behavior remains aligned with automation.
-
Create a TradingView strategy alert using Order fills only.
-
Paste the provider’s exact native message into TradingView’s Message field.
-
Paste the provider webhook URL.
-
Test long, short and every enabled exit path in demo/minimum size.
| Provider-Native kill switch Turning Use Automation OFF inside Pine is not a dependable emergency stop for an already-created provider-native alert, because TradingView can continue sending the alert dialog’s provider message on strategy fills. Pause/delete the TradingView alert and/or stop the provider bot. |
|---|
Provider setup instructions
The provider-generated message and webhook URL are unique to each selected bot and require the matching source workflow. Choose the complete provider-specific instructions:
Use the instructions for the TradingView Strategy signal source, rather than mixing an indicator alert() workflow with TradeSmart V2 strategy order fills.
Other provider-native services
| Provider/service | Recommended V2 route | Key note |
|---|---|---|
| Tickerly | Provider-Native or Custom | Use its documented standard/swing alert structure. Match swing/reversal semantics. |
| SignalStack | Provider-Native | Use the webhook/configuration generated for the connected broker route. |
| Autoview | Provider-Native / service syntax | Use its current strategy-alert command syntax; browser/extension execution has different operational risks from server-side bots. |
| Alertatron | Provider-Native / Custom | Use its current signal format and bot routing. |
| PickMyTrade | Provider-Native | Use the TradingView JSON/webhook setup generated for the linked account. |
| CrossTrade | Provider-Native / Custom | Confirm NinjaTrader/account reversal and flatten behavior before enabling one-step reversals. |
| Capitalise.ai | Provider-Native | Use TradingView alerts as triggers according to the strategy created in Capitalise.ai. |
| TradingConnector | Provider-Native / Custom | Follow the current connector payload and account routing. |
| WebhookTrade | Provider-Native / Custom | Verify quantity and partial-close semantics. |
| Cornix | Provider-Native | Use the current Cornix TradingView webhook/bot workflow. |
| Cryptohopper | Provider-Native | Use its TradingView/webhook signal configuration. |
| HaasOnline | Provider-Native / Custom | Use the current webhook/signal command expected by the Haas bot. |
| ProfitView | Provider-Native / Custom | Use its current TradingView alert syntax and exchange mapping. |
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.
Choose your provider’s exact setup guide
- 3Commas — step-by-step TradingView Strategy Signal Bot: creating a bot, choosing the signal source, copying the bot’s own payload, validating positions and logs.
- WunderTrading — step-by-step Signal Bot setup: create the exchange connection, choose Strategy source, copy bot-specific JSON/webhook and test live routing on demo.
These are two distinct providers. Never reuse one bot’s credentials, endpoint or message template with the other.
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.