TradingView webhook setup and troubleshooting

This category covers the current TradingView workflow in DaneTrades: creating the TradingView source account, using the webhook builder guidance, sending valid JSON alerts, handling closes correctly, and fixing the two recurring delivery issues: tunnel problems and outdated webhook URLs.

Start here Open Copiers

Built around the current TradingView webhook builder and signal-based connection flow
Covers alert JSON, closes, risk sizing with SL, tunnel status, and webhook security
Designed to reduce missed alerts, bad payloads, and stale webhook URL issues

Recommended order

Read these in sequence for a safer TradingView setup

Start here: TradingView. Understand the overall workflow first.
Set up the TradingView webhook source. Create the account, get the webhook URL, and create the first connection.
Supported JSON formats and examples. Keep the payload valid and minimal before adding more logic.
Close signals and alert-message setup. Avoid the common close-action trap in TradingView alerts.
Risk sizing requires stop loss. Only matters if you use risk-based sizing on the copier.
Tunnel not running or webhook URL changed. Fix delivery first if alerts stop arriving.
Common mistakes and webhook security. Clean up weak or brittle setups after the basics work.

Articles

Current TradingView guides

These guides are aligned to the current TradingView account flow, webhook builder copy, and signal-based connection behavior in the app.

Orientation

Start here: TradingView

Understand the current workflow for webhook setup, alert payloads, connection creation, and first troubleshooting steps.

Read article

Setup

Set up the TradingView webhook source

Create the TradingView source account, copy the current webhook URL, and link it to a supported receiver account.

Read article

Payloads

Supported JSON formats and examples

Use valid alert payloads with the correct field names so webhooks arrive as usable trading actions instead of malformed text.

Read article

Closes

Close signals and alert-message setup

Handle closes explicitly and understand when the current app prefers custom alert JSON over fragile placeholders.

Read article

Risk sizing

Risk sizing requires stop loss

Use SL correctly when the copier relies on risk percent or risk dollar sizing.

Read article

Delivery

Tunnel not running or webhook URL changed

Fix the two most common alert-delivery failures before you spend time changing payload logic.

Read article

Hardening

Common mistakes and webhook security

Catch brittle TradingView setups early and protect webhook endpoints with a secret token.

Read article

Common Questions

TradingView webhook FAQ

These are the setup questions most people hit when they move from TradingView alerts into live webhook-driven copying.

Do I need a paid TradingView plan for webhooks?

Yes. TradingView webhook alerts require a paid TradingView plan. If the plan does not support webhooks, the DaneTrades side can be configured correctly and still receive nothing.

Why did TradingView alerts stop arriving after I restarted the app?

The local runtime can generate a new webhook URL when the app restarts or the tunnel refreshes. Each TradingView alert stores its own URL, so you need to copy the current URL from the app and update those alerts manually.

Should I send an explicit close action from TradingView?

Yes. Explicit close JSON is the safer path because some TradingView placeholders only express buy or sell cleanly and can make exit logic harder to control.