TLDR: A TradingView alert can trigger without sending a webhook. Open the alert's Notifications settings and confirm Webhook URL is enabled, the exact URL is present, two-factor authentication is active, and the notification schedule permits delivery at that time. TradingView's notification schedules can block outbound channels, including webhooks, while still recording the trigger in the alert log. Also remember that alert presets do not save webhook URLs.
Stop Executing Trades By Hand.
UMT Automator turns your TradingView or NinjaTrader strategy into automatic, hands-free execution — no code, no webhooks, no missed signals. Prefer a ready-made edge? Browse UMT's tested Strategies & Indicators built for both platforms.
Free 7-day trial on the Automator · No credit card required
This problem sits between the alert condition and HTTP delivery. If there is no alert-log event, troubleshoot the condition. If there is an event but no webhook attempt, inspect notification configuration. If the Webhook status shows a failure, troubleshoot the endpoint using the exact error.
Traders who want to avoid configuring webhook notifications can evaluate UMT Automator, a browser-based workflow for eligible TradingView strategies that does not require a user-configured webhook, JSON alert payload, broker API key, or middleware server.
Start With the Alert Log
Locate the expected event in TradingView's Alerts Log. Three outcomes lead to three different investigations:
- No trigger exists: inspect the alert condition, frequency, expiration, strategy copy, and realtime data.
- The trigger exists but the webhook channel was not used: inspect Notifications, the schedule, the URL field, and 2FA.
- The trigger exists and Webhook status failed: inspect the error code, receiver, and network path.
Do not start by editing the server if TradingView never attempted the webhook.
Is Webhook URL Enabled in the Alert?
Edit the alert and open its Notifications tab. Confirm that Webhook URL is selected and that the intended production endpoint appears in the field. An email, app notification, popup, or sound selection does not automatically enable webhooks.
Inspect the actual alert, not only the create-alert form or a template you expect it to use. Saved configurations and duplicated alerts can preserve settings that differ from the current form.
Is a Notification Schedule Blocking the Webhook?
TradingView introduced alert notification schedules in July 2026. The schedule controls when outbound notifications may be delivered. Outside its active period, configured channels, including webhooks, are blocked even though the alert trigger is still recorded in the log.
This creates a distinctive symptom: the condition triggered on time, but no webhook left TradingView. Open the calendar control in the Notifications tab and inspect:
- The active days of the week.
- The start and end times.
- The account timezone used by the schedule.
- Whether the alert inherited a previously used schedule.
- Whether a one-time alert's second-chance option is relevant.
For an automation that is intended to send continuously, TradingView advises keeping the notification schedule at 24/7. Only choose a narrower window when suppressing notifications outside that window is intentional and safe.
Why Can the Schedule Be Easy to Miss?
TradingView says notification schedules are sticky, which means a recently used setting can carry into newly created alerts. Schedules can also be stored in alert presets. A trader may therefore recreate an alert and unknowingly restore the same restricted delivery window.
Check the schedule after using a preset or duplicating an alert, especially when the failure occurs only overnight, on certain weekdays, or after a timezone change.
Did an Alert Preset Restore the Webhook URL?
No. TradingView's alert-preset documentation explicitly says webhook URLs are not saved in presets. A preset can restore other alert settings, but you must enter and verify the webhook URL separately.
This commonly explains why a newly recreated alert looks correct while its webhook field is empty. Treat the endpoint as a required post-preset check.
Is Two-Factor Authentication Enabled?
TradingView requires two-factor authentication to use webhook alerts. Confirm that 2FA remains enabled on the account and that the Webhook URL control is available. Do not weaken account security to troubleshoot automation.
Never put account credentials or passwords in the webhook body or URL. TradingView also warns against sending sensitive information in webhook messages.
Is the Alert Active, Current, and Based on the Right Copy?
Verify that the alert is active rather than stopped or expired. For script and strategy alerts, TradingView saves a server-side copy of the script, inputs, symbol, and timeframe when the alert is created. Later chart or code changes do not update the running alert automatically.
If you changed the strategy, its inputs, symbol, or timeframe, delete the obsolete alert and create a new one from the intended configuration. Recreating an alert is also the right time to recheck Notifications, schedule, URL, and message.
Did TradingView Attempt Delivery?
Display the Webhook status column in the alert log. An HTTP error, timeout, invalid URL, TLS problem, or refused connection proves that TradingView attempted delivery and reached a different failure stage.
TradingView supports only destination ports 80 and 443 for webhook requests, requires a publicly reachable address, and does not support IPv6 delivery. The receiver must answer within three seconds or TradingView cancels the request.
A Safe Test for the Webhook Notification Channel
- Use paper trading or a non-ordering diagnostic endpoint.
- Create one controlled alert with a condition you can trigger deliberately.
- Enable Webhook URL and paste the exact test endpoint.
- Set the notification schedule to include the test time.
- Use a unique, non-sensitive message identifier.
- Trigger once and compare the alert log with receiver logs.
If that test works, compare its settings field by field with the failed alert. Change one variable at a time.
When the Alert Trigger Is the Real Problem
If the expected event does not exist in the alert log, the notification channel cannot send anything. Investigate whether the alert requires a crossing event, waits for bar close, uses a stale strategy copy, or was stopped after rapid triggering. TradingView documents that a strategy alert stops if it triggers more than 15 times within three minutes.
How UMT Automator Avoids Webhook Notification Setup
UMT Automator connects supported TradingView strategy activity with broker-side automated trade execution through a browser-based workflow. The user does not configure a TradingView Webhook URL, build JSON messages, manage broker API keys, or host a receiver.
The workflow still depends on an eligible TradingView strategy, supported setup, the browser and required tab remaining open, a stable internet connection, and broker availability. It does not guarantee alert delivery, execution, fills, or results.
Review how to get started with UMT Automator, then use the current free 7-day trial to evaluate whether the workflow fits your automation process.
Frequently Asked Questions
Can a TradingView alert trigger without sending its webhook?
Yes. A notification schedule can block the webhook channel while the trigger remains in the alert log. The Webhook URL action can also be disabled or empty.
Are TradingView webhook URLs saved in alert presets?
No. TradingView says webhook URLs are not saved in presets. Enter and verify the URL whenever you create an alert from a preset.
Should an automated TradingView alert use a 24/7 notification schedule?
If uninterrupted outbound delivery is intended, TradingView advises leaving the schedule at 24/7. A narrower schedule intentionally suppresses channels outside the selected window.
Do TradingView webhooks require 2FA?
Yes. TradingView requires two-factor authentication for webhook alerts.
Risk disclaimer: Automated trading involves substantial risk. Test alert and order workflows in simulation or paper trading before live use. A successful alert or webhook does not guarantee broker acceptance, execution, fill price, or profitability.
