What you will learn in this lesson
- Briefly recap the general webhook concept before going hands-on
- Locate the "Webhook URL" field inside TradingView's own alert creation dialog
- Understand what happens, mechanically, when an alert with a webhook URL fires
- See how this builds directly on the Module 8 alert lessons already covered
- Prepare for Lesson 40's deeper look at the alert message and its placeholders
Module 8 taught you to set alerts - conditions that notify you when something happens on the chart. This lesson looks at one specific field inside that same alert dialog: Webhook URL - the setting that lets an alert message another system automatically, instead of (or alongside) simply notifying you.
A Brief Webhook Recap
A webhook is an automated message that one system sends to another system when a specific, predefined event occurs. If this is genuinely new to you, and you’d like the simple concept from scratch, see What Is a Webhook? Explained for Non-Programmers first - it covers the general idea in depth, with a doorbell-camera analogy and no TradingView specifics assumed.
This lesson assumes that basic recap is enough, and goes straight into TradingView’s own mechanics: specifically, where this capability lives inside the alert dialog you’ve already used, and what happens when it fires.
Where the Webhook URL Field Lives
Recall the alert creation dialog from Module 8 - the same window used to set a price alert or an indicator-based alert. Inside that same dialog, typically under a “Notifications” section alongside other notification checkboxes (app notification, email, and so on), there’s a field labelled Webhook URL.
TradingView Alert Dialog (same one from Module 8)
────────────────────────────────────────────────
Condition: [ price crosses 24,200 ▾ ]
Alert name: [ ................... ]
Message: [ ................... ] ← Lesson 40 covers this
──────────────────────────────────────────
Notifications:
[ ] App notification
[ ] Email
[ ] Webhook URL: [ ......................... ] ← this lesson
This field is optional - alerts already worked perfectly fine throughout Module 8 without ever touching it. Filling it in adds one more thing that happens when the alert fires: a message sent automatically to whatever address is entered there.
What Happens When It Fires
Mechanically, the sequence is straightforward:
- The alert’s condition (a price level, an indicator condition - anything from Module 8) is met.
- TradingView fires the alert, exactly as it already would for an on-screen or app notification.
- If a Webhook URL was entered, TradingView additionally sends an HTTP message to that address, carrying the alert’s configured message content (Lesson 40 looks closely at what goes into that message).
- Whatever system is listening at that URL receives the message and does whatever it’s built to do with it - a detail entirely outside TradingView’s control, covered further in Lesson 41’s workflow overview.
Alert condition met → TradingView fires alert → HTTP message sent
to Webhook URL
│
▼
Receiving system gets it
(what happens next is
up to that system)
Real-Life Example: Adding a Webhook to a Familiar Alert
Suppose a trader already has a Bank Nifty price alert set up from Module 8 - “notify me if price crosses 51,500.” Returning to that same alert’s settings, they scroll to the Notifications section and paste a URL into the Webhook URL field - a URL provided by a receiving system they intend to use. Nothing else about the alert changes: the condition, the instrument, everything from Module 8 stays exactly the same. The only difference is that, in addition to (or instead of) an on-screen notification, TradingView now also sends that same alert event as a message to the specified URL, automatically, the moment the condition triggers.
Analogy: An Extra Address on a Notification Form
Think of the alert dialog like a form you’ve already filled out many times (Module 8): condition, name, message. The Webhook URL field is simply one more line on that same familiar form - an extra address to CC, in a sense. Everything else about the form stays the same; you’re just adding one more place the notification gets sent, automatically, alongside (or instead of) your own phone or inbox.
Common Beginner Mistakes
- Assuming webhooks are a separate feature from the alerts already learned in Module 8. They’re one additional field inside that exact same familiar dialog.
- Confusing this lesson with the general webhook concept lesson. This lesson goes hands-on with TradingView’s specific field and mechanics - see the linked conceptual lesson above if the general idea itself is still unfamiliar.
- Believing the Webhook URL field is mandatory for alerts to function. It’s entirely optional - alerts work fine with only on-screen or app notifications, exactly as used throughout Module 8.
- Expecting TradingView to control what happens after the message is sent. TradingView’s responsibility ends at sending the HTTP message - what the receiving system does with it is entirely separate, covered in Lesson 41.
Practical Tips
- Open a familiar alert from your own Module 8 practice and simply locate the Webhook URL field - no need to enter anything yet, just build familiarity with where it lives.
- Keep the distinction clear: the CONDITION (Module 8) is unchanged by adding a webhook - only the NOTIFICATION side gains an additional automatic recipient.
- Read Lesson 40 next before entering any real URL - understanding the message box and its placeholder syntax first makes the whole picture click into place.
Practical Exercise
- Open the alert creation dialog on TradingView (the same one used in Module 8) and, without saving or activating anything, simply scroll down to locate the "Webhook URL" field and the message box beneath or near it. Note what you see.
- Write 2-3 sentences, in your own words, describing what you'd expect to happen - mechanically - between "an alert condition is met" and "a message arrives somewhere else," based on this lesson.
Mini Quiz
1. What is a webhook, in the simplest possible recap?
A webhook is an automated message sent from one system to another when a specific, predefined event happens - a brief recap of the concept covered fully elsewhere, before this lesson goes hands-on with TradingView specifically.
2. Where is the "Webhook URL" field located when creating a TradingView alert?
The Webhook URL field lives inside TradingView's own alert creation dialog - the same dialog used to configure price alerts and indicator alerts back in Module 8 - typically alongside the alert's message box.
3. What happens, mechanically, when a TradingView alert configured with a webhook URL fires?
When the alert condition is met, TradingView automatically sends an HTTP message to whatever URL was entered in the Webhook URL field - carrying the alert's configured message content to that destination.
4. Does this lesson replace the need to understand the general webhook concept from the other, more conceptual lesson in this course's sister module?
This lesson builds on the general webhook concept with TradingView-specific, hands-on mechanics (the actual dialog field, message box). A reader wanting the simple concept from scratch should see the dedicated conceptual lesson referenced in this lesson's body.
5. Why does this lesson build specifically on Module 8's alert lessons?
The webhook URL field is simply one additional field within the same alert creation dialog covered in Module 8 - this lesson doesn't introduce a separate feature, but extends what's already familiar with one more configuration option.
Frequently Asked Questions
I've never heard of webhooks before - should I read something else first?
If you want the simple concept from scratch, see [What Is a Webhook? Explained for Non-Programmers](/academy/fo-beginner-course/what-is-a-webhook), which covers the general idea with no TradingView-specific mechanics assumed. This lesson briefly recaps that concept, then goes straight into TradingView's own alert dialog specifically.
Where exactly do I find the Webhook URL field?
It's inside the same alert creation dialog used throughout Module 8 (the one opened when setting up a price or indicator alert) - look for a field labelled "Webhook URL," typically found under the "Notifications" section of that dialog, alongside checkboxes for other notification types.
Do I need to fill in the Webhook URL field for a TradingView alert to work at all?
No - it's entirely optional. Alerts can be (and commonly are) used purely with on-screen or app notifications, as covered in Module 8, without ever touching the Webhook URL field. Filling it in is only necessary when you specifically want the alert to also message another system automatically.
What does TradingView actually send when a webhook-configured alert fires?
It sends an HTTP message to the configured URL, carrying whatever content was written in the alert's message box - Lesson 40 covers this message box and its placeholder syntax in detail.
Does the receiving system need to be built by TradingView itself?
No - the Webhook URL field simply needs a valid address for whatever receiving system you intend to use; that system is entirely separate from TradingView and must be built or configured (by you or a platform you use) to actually listen for and process the incoming message.
Can I test whether a webhook URL is working without a real trading condition happening?
TradingView alerts commonly support ways to test or manually trigger notifications during setup - checking current TradingView documentation for the exact current testing options available is worthwhile before relying on any webhook-based setup for anything important.
Is setting the Webhook URL field itself considered "automation"?
It's one necessary building block toward automation, specifically the messaging mechanism - but automation as a broader concept (covered in Module 12) is about what happens on the receiving end with that message, not merely the act of sending it.
Does every TradingView plan tier support webhook URLs in alerts?
Feature availability by plan tier can change over time - always check TradingView's current plan comparison directly for the most up-to-date details on which tiers include webhook-capable alerts.
What's the very next thing this course covers after this lesson?
Lesson 40 looks closely at the alert's message box itself - specifically TradingView's placeholder syntax (like {{ticker}} or {{close}}) and how to compose a simple structured message using it.
Is there any risk in filling in the Webhook URL field incorrectly?
A mistyped or unintended URL simply means the message won't reach the intended destination (or could reach an unintended one, if entered carelessly) - Lesson 42 covers webhook security practices in more depth, including being careful about exactly what gets entered here.
Glossary
Key Takeaways
- A webhook, recapped briefly, is an automated message one system sends to another when a specific, predefined event occurs.
- TradingView's "Webhook URL" field lives inside the same alert creation dialog already used for price and indicator alerts in Module 8.
- When a webhook-configured alert fires, TradingView automatically sends an HTTP message to that URL, carrying the alert's message content.
- Filling in the Webhook URL field is entirely optional - alerts work fine with only on-screen or app notifications, as covered in Module 8.
- This lesson goes beyond the general webhook concept into TradingView-specific, hands-on mechanics - the dedicated conceptual lesson elsewhere covers the simple idea from scratch.
Conclusion
The Webhook URL field is just one more setting inside the same alert dialog you've already used since Module 8 - but it's the specific piece that turns a chart condition into a message sent automatically to another system. The next lesson looks closely at what goes into that message itself, including TradingView's placeholder syntax for building something a receiving system can actually use.
