How to Automate Trading Alerts to Discord (10-Minute Setup)

I spent two years checking my phone during market hours because I didn't have a reliable alert system. I'd miss setups, then feel like I had to watch screens constantly to compensate. When I finally wired TradingView alerts into a dedicated Discord channel, that changed. Alerts showed up the moment a condition was met -- on desktop, mobile, even on my Apple Watch -- without any active screen monitoring on my end.

This guide walks through two methods. The first is a direct TradingView-to-Discord connection using a webhook URL -- zero code, zero cost beyond TradingView's Essential plan, done in under 10 minutes. The second uses Make.com to add formatting, conditional logic, and multi-destination routing for traders who want more control over what gets sent and when. Either way, you'll end the session with a live alert system firing into Discord in real time.

Why Discord Beats Email and SMS for Trade Alerts

Email alerts are too slow -- a 30-second delay is common, and longer delays happen regularly during high-volume market events when every alert service is under load simultaneously. SMS costs money at scale and doesn't support any kind of structured formatting. Telegram works but the notification grouping is awkward for high-frequency alerts, and the desktop client doesn't give you the persistent, organized channel structure that Discord does.

Discord channels behave like a persistent, searchable feed. You can create separate channels for different strategies, pin the most important alerts, search through historical messages by keyword, and share a server with your trading group without any subscription fees. The free tier supports unlimited channels, unlimited message history, and full webhook functionality. That combination -- organized, searchable, free, and accessible on every device -- makes it the best landing spot for automated trade alerts.

What you can route to Discord

• Price alerts when a ticker crosses a specific level or percentage move threshold
• Indicator alerts for RSI hitting oversold, MACD crossovers, Bollinger Band squeezes, or volume spikes
• Custom Pine Script conditions from any TradingView indicator or strategy script
• News or earnings calendar alerts via a Make.com webhook trigger
• Scheduled trading journal reminders via Make.com time-based triggers
• Broker fill confirmations for supported brokers via Make.com integrations

Step 1: Create Your Discord Channel and Get a Webhook URL

Before touching TradingView, get the Discord side ready. You need a server you own or have administrator access to, plus a dedicated channel where the alerts will land. Don't set up automated alerts in a shared community server unless you're the owner -- creating webhooks requires administrator rights that most community members don't have.

Step 2: Connect TradingView Directly to Discord

TradingView's alert system includes a native webhook field. When an alert condition fires, TradingView sends an HTTP POST request to the URL you specify, with a message body you define in the alert dialog. Discord webhooks accept POST requests in a specific JSON format -- so the two services connect directly, with no middleware or proxy layer required.

The critical detail: Discord expects a JSON body with a 'content' key containing your message text. TradingView sends exactly that if you format the message field correctly in the alert dialog. The message you write becomes the body of the POST request, so it needs to be valid JSON -- no curly quotes, no trailing commas, proper key-value structure.

TradingView placeholders worth knowing

Step 3: Add Make.com for Richer Formatting and Conditional Routing

Make.com (formerly Integromat) is a no-code automation platform where you build visual workflows called scenarios. A scenario receives a TradingView webhook, applies formatting or conditional logic, and then posts to Discord -- or to multiple destinations simultaneously. This method adds roughly 20-30 minutes of setup time but unlocks capabilities the direct webhook connection cannot deliver.

When Make.com is worth the extra setup time

The direct TradingView-to-Discord webhook handles 90% of use cases cleanly. Make.com earns its place when you want to route long alerts to one channel and short alerts to a separate channel automatically, when you want to log every alert to a Google Sheet at the same time as posting to Discord, or when you want Discord's embed format -- color-coded cards with structured fields -- instead of plain text messages.

Common Mistakes and How to Fix Them

Most problems with this integration come down to JSON formatting errors or alert frequency settings. These are the issues I see most often when traders first wire up TradingView to Discord, and all of them are straightforward to diagnose and fix.

Webhook fires but nothing shows in Discord

Check your JSON format first. Discord rejects malformed JSON silently -- TradingView shows the alert as 'sent' but nothing arrives in the channel. Paste your message payload into jsonlint.com to validate it before saving the alert. The two most common errors are missing double quotes around the 'content' key and using curly (smart) quotes instead of straight quotes. Curly quotes look similar but break JSON parsing completely.

Getting too many or duplicate alerts

Check the alert frequency setting in TradingView. 'Every time condition is met' fires on every price tick while the condition remains true -- for a price-above condition on a 1-minute chart, that's potentially hundreds of alerts per hour. Switch to 'Once Per Bar Close' for most conditions. If you only want a single notification when a level is first broken, use 'Only Once'. In Make.com, you can also add a duplicate filter that suppresses alerts from the same ticker within a configurable cooldown window.

Make.com scenario runs but Discord shows an error

Open the execution log in Make.com and look at the Discord module output. Error 400 means a malformed message payload -- check the JSON structure of your Discord message. Error 429 means you hit Discord's rate limit -- add a delay module between the webhook trigger and Discord module to throttle delivery. Error 50006 means you're sending an empty message -- add a Make.com filter that verifies key fields like ticker and price are not empty strings before the Discord module runs.

What to Do Next

Start with Method 1 -- the direct TradingView webhook. Get one alert firing into Discord today. The whole setup takes under 10 minutes, and you'll immediately see whether the alert message format works for how you actually trade in real time. If the plain-text format is enough, you're done. If you want routing, richer formatting, or logging, layer in Make.com after you've validated the basics.

A few things worth setting up once your first alert is live: create separate channels for different setup types (opening range breakouts in one channel, VWAP reclaims in another), pin the most important recurring alerts so they're easy to find during fast-moving sessions, and consider inviting your trading group or accountability partner to the server so everyone gets the same signal at the same moment.

Automating alerts doesn't replace reading the tape or doing your own pre-market analysis -- it removes the need to watch 10 tickers simultaneously while trying to stay focused and rested. The automation handles the monitoring; your judgment handles the trade decision. That division of labor is what makes the system genuinely useful rather than just an interesting technical project.