Smart Trading Bot
TradingView alerts, captured and compared.
Send live alert rows into one webhook, store the raw payload exactly as received, and let the platform build sample trades from the sequence.
Webhook Layer
One public listener for TradingView alerts, with exact raw rows saved first.
The new flow starts by capturing every webhook payload exactly as TradingView sends it. Nothing is rebuilt into Pine-side candles first, which makes debugging faster and comparisons more honest.
Each incoming alert is stored with symbol, timeframe, action, prices, quantity, and the full original JSON payload.
Hidden files, SQL dumps, logs, and internal folders are blocked from public web access so the live server does not leak internals.
The admin monitor surfaces the live webhook URL, example JSON, recent alerts, and generated sample trades in one place.
Rows arrive through a direct URL, are validated, stored, and marked with their processing result immediately.
TradingView posts a JSON row into the live webhook URL.
The exact payload is stored before any comparison logic runs.
Entry, exit, and reversal rows are matched into sample trades for review.
No candle conversion layer stands between the alert and the database row you inspect later.
Comparison Engine
Raw alert rows that turn into trackable sample trades without replaying Pine logic on the server.
Instead of rebuilding candles and trying to mirror Pine internals, the platform now evaluates the sequence of received TradingView alerts and stores the sample trade outcome directly.
The saved row stays aligned to what TradingView actually sent, which makes mismatch analysis faster.
Long, short, exit, and reversal events are grouped into a separate sample-trade table for testing accuracy.
Every saved row records whether it opened a trade, closed one, reversed one, duplicated an entry, or was stored as raw only.
Metrics Desk
Reports that show the webhook row, the inferred trade, and the result side by side.
The monitor highlights recent raw alerts, open sample trades, closed sample trades, and the running sample PnL so you can judge how close the alert sequence is to the expected behavior.
The database keeps both the original alert row and the generated sample trade so the comparison stays auditable.
Broken alert patterns are easy to isolate because every row carries its own processing note and linked trade ID.
Payment flows, settings changes, and webhook activity stay traceable from the same admin surface.
Sample trade records stay aligned to the real alert sequence coming from TradingView, not recreated candles on the server.
Launch Ready
Open the dashboard, wire TradingView once, and start validating alert accuracy.
Register with sponsor mobile number, verify OTP, connect exchange access if needed, and use the new webhook monitor to inspect raw rows and sample trades.