For IC Markets users who already have alerts and want reliable execution instead of manual relay work.
That makes broker-specific issues easier to isolate and fix.
- Status
- Requested / planned support
- Asset classes
- Forex, indices, commodities
- Flow
- TradingView -> Vorda -> IC Markets
- Common issues
- Lot sizing, symbols, order rules
IC Markets setup notes
- Start with the broker account the trader already uses.
- Show the execution path from webhook to broker response.
- Use sandbox testing before live account routing.
IC Markets users want routing clarity
The trader usually already trusts IC Markets. The open question is how to route the TradingView signal into that account without relying on a brittle manual or semi-manual workflow.
The setup needs to show how the webhook is received, checked, mapped, and sent to the broker.
Broker-specific execution details still matter
Even when the signal is correct, broker- or exchange-specific rules can still block the trade. Symbol mapping, lot sizing assumptions, and accepted order types are the most common reasons the path breaks.
A visible routing layer makes those issues fixable without deep support escalation.
Test the route before live automation
The safest next action is to test the flow in sandbox and confirm that the IC Markets route behaves as expected before any live automation is turned on.
The first live run should not be the first time you see the parsed payload, symbol mapping, or account checks.
FAQ
Answers users search for before connecting automation.
What should I test first with IC Markets automation?
Test the alert payload, symbol mapping, and execution log flow before connecting the live account.
What if support is not fully live yet?
Request the broker or exchange while still validating the rest of the TradingView automation flow in sandbox.