How zorrong/tradingview-webhook-mt5-bridge works
This is a Windows Forms TradingView-to-MetaTrader webhook bridge. A trader configures and starts the local listener, then TradingView alerts arrive as JSON, are checked and transformed into order instructions, and are relayed toward MetaTrader; the UI displays status and alert outcomes. The sampled C# shows the listener, request processing, named-pipe transmission, and UI logging, but does not establish the full validation, risk, replay, or broker-side implementation. Those branches reflect README capabilities, not inspected implementation details.
Main entry points: Form1.cs Request handling · Program.cs App entry · Form1.Designer.cs Status and alerts · TradingViewToMT5 JSON validation
Components 15
Desktop app
- App entry
TradingViewToMT5/Program.cs - Bridge UI
TradingViewToMT5/Form1.cs - Status and alerts
TradingViewToMT5/Form1.Designer.cs
Alert handling
- Webhook listener
TradingViewToMT5/Form1.cs - Request handling
TradingViewToMT5/Form1.cs - JSON validation
TradingViewToMT5 - Template and symbols
TradingViewToMT5 - Alert safeguards
TradingViewToMT5 - Audit and replay
TradingViewToMT5
Order execution
- Risk sizing
TradingViewToMT5 - Order routing
TradingViewToMT5 - Named-pipe relay
TradingViewToMT5/Form1.cs
Other components
- Trader
- TradingView
- MT4 / MT5
Connections 15
- App entry → Bridge UI: opens
- Trader → Bridge UI: configures
- Trader → Webhook listener: starts
- TradingView → Webhook listener: posts alerts
- Webhook listener → Request handling: dispatches
- Request handling → JSON validation: checks payload
- Request handling → Template and symbols: maps fields
- Request handling → Alert safeguards: applies rules
- Request handling → Audit and replay: records alert
- Request handling → Risk sizing: sizes order
- Request handling → Order routing: routes order
- Request handling → Named-pipe relay: transmits command
- Named-pipe relay → MT4 / MT5: relays to
- Request handling → Status and alerts: updates alert
- Bridge UI → Webhook listener: controls