Use TradingView for the alert, then let Vorda validate it through exact Trading Rules and compatible connected accounts.
Create the source-owned webhook and test the generated message safely. Source testing never places a trade.
- Best for
- Broker and exchange execution routing
- Signal source
- TradingView webhook alerts
- First step
- Start free sandbox
- Core value
- Multi-broker and exchange visibility and control
Key takeaways
- A Signal Source owns the private webhook and can be configured and tested before an Automation exists.
- Validation, routing, and execution logs matter more than simply firing a webhook.
- The safest first run is a sandbox test before any live credentials are connected.
Direct answers for traders setting up TradingView automation.
Can TradingView execute trades automatically?
TradingView can send the alert automatically, but a separate execution layer still needs to receive the webhook, validate it, and route it to the broker or exchange.
Which destinations can receive TradingView actions through Vorda?
Vorda currently supports Pepperstone cTrader, IC Markets cTrader, Alpaca, Binance Spot, Binance Futures, and Hyperliquid. Compatibility is checked when the source, Rules version, and accounts are bound in an Automation.
What happens after a TradingView alert fires?
The webhook is received, the payload is parsed, risk and routing checks run, the destination broker or exchange is selected, and the result is written to logs so the user can see what happened.
Current Vorda product scope
Supported destinations are Pepperstone cTrader, IC Markets cTrader, Alpaca, Binance Spot, Binance Futures, and Hyperliquid. Signal Sources can be tested independently. Execution authority exists only in a compatible, ready, running Automation with an immutable Trading Rules version.
AI Agent availability starts with vorda.propose_action. Account visibility, history, previews, and controlled actions are planned until their MCP tools are released.
Use TradingView as the signal source, not the execution engine
A TradingView alert is only the signal. Something still has to receive the webhook, identify the destination account, validate the symbol and order details, and decide whether the order is allowed to reach the broker or exchange.
Vorda sits in that middle layer. Your TradingView logic can stay in TradingView while routing, validation, and execution logs live in one place.
Bind the source to compatible accounts through an Automation
The Signal Source does not choose a destination. An Automation binds it to one exact Trading Rules version and one to three compatible broker accounts.
That separation lets the same accepted source alert fan out through multiple active Automations while preserving account-specific validation, reconciliation, and proof.
Make execution visible enough to troubleshoot and trust
The important part starts after the alert fires. You need to know whether the payload was accepted, blocked by a rule, rejected by the broker or exchange, or filled.
That record is what makes testing useful. When the sandbox log is readable, you can fix the payload, symbol, or account setup before a live trade is involved.
FAQ
Answers users search for before connecting automation.
Can one TradingView source feed more than one Automation?
Yes. One source can feed multiple active Automations. Each Automation independently binds its Rules version and compatible target accounts, so one failure does not block the others.
What is the safest way to start?
Start in sandbox first. Validate the webhook payload, test the symbol mapping, inspect the logs, and only then connect live credentials.