I run a small Discord server for a side project, and for months I would only find out about a new form submission when I happened to log in and check manually, sometimes days late. Building a Make.com scenario to post an alert the moment a form came in changed that completely, and it took less time to set up than I expected. This guide covers both Discord and Slack, since the setup differs slightly between the two, plus the part that actually matters most: deciding what deserves an alert in the first place.
How Do You Send Automatic Notifications to Slack or Discord with Make.com?
The pattern is the same regardless of which chat app you use: a trigger detects something worth noting, like a new row in a spreadsheet, a webhook firing from a form, or a new item in an RSS feed, and the scenario ends with a message module that posts the details into a channel. Discord and Slack differ mainly in how you connect them, not in the overall shape of the scenario.
Discord relies on a webhook URL, a simple link tied to one specific channel. Slack relies on an authorized app connection tied to your whole workspace, letting you choose the channel per message instead. Both are beginner-friendly once you know which route to take.
How Do You Set Up Discord Webhook Notifications?
Inside Discord, open the settings for the channel you want messages to land in, find the integrations section, and create a webhook. Discord gives you a unique URL for that webhook, which is essentially a private door that lets outside tools post messages into that specific channel without needing a full bot setup.
In your Make.com scenario, add a module for sending an HTTP request, or Make's dedicated Discord module if you are using one, and paste that webhook URL in. Set the message text, including any dynamic details pulled from earlier in the scenario, like a person's name or the content of a submission, and connect it as the final step. Run the scenario once as a test, and you should see the message appear in Discord within seconds.
Keep that webhook URL private. Anyone who has it can post into that channel, so treat it the same way you would treat a password, and avoid pasting it somewhere public like a shared document.
How Do You Connect Slack to Make.com?
Slack works a little differently. Add a Slack module to your scenario and choose to create a new connection, which opens a login and approval screen for your Slack workspace. Approve the access Make requests, and the connection is saved for reuse across any scenario in your account, not just this one.
From there, add a send message action, choose which channel it should post to, and write your message content. Slack's connection model means you can post to different channels from different scenarios without setting up a separate webhook for each one, which is convenient once you have more than one type of alert running.
What Kinds of Alerts Are Actually Worth Sending?
This is the part most beginners skip past, and it is where the real value lives. A few categories that actually earn a real-time alert:
- Form submissions. Someone took an action and is likely expecting a timely response, whether that is a lead, a support request, or a signup.
- Calendar reminders. An upcoming meeting or deadline that benefits from a nudge you might otherwise miss while heads-down elsewhere.
- New content from an RSS feed. A source you actively follow, where being a little late truly means missing something.
The test I use before wiring up any new alert: would I actually stop what I am doing to read it the moment it lands? If the honest answer is no, it belongs in a summary instead of a real-time ping.
How Do You Keep Notifications From Becoming Noise?
The fastest way to kill trust in an automated alert channel is flooding it with things nobody needed to see immediately. A few habits that have kept mine useful instead of ignored:
- Filter aggressively before the message step. Our guide to filters and routers covers how to only let truly relevant events reach your notification module, instead of alerting on everything.
- Batch low-priority updates. Instead of a message per item, collect them and send one daily or weekly summary. This works especially well for anything that is nice to know but not urgent.
- Separate channels by urgency. Route time-sensitive alerts into one channel and everything-else updates into another, so people can mute what they do not need without missing what they do.
- Prune regularly. Every so often, check whether an alert type is actually getting read or has quietly become background noise everyone tunes out. If it is the latter, cut it or fold it into a summary.
The same trigger sources that feed these notifications, like a scheduled check on a spreadsheet or feed, pair naturally with the scheduling choices covered in our guide to running scenarios on a timer, since how often you check something directly affects how promptly, or how noisily, your alerts arrive.
Can You Send the Same Alert to Both Slack and Discord?
Yes, and it is a small addition once one path works. After your trigger and filter logic, add both a Slack message module and a Discord webhook module in the same scenario, so a single event posts to both places at once. I did exactly this during a stretch when part of my team was still on Slack while the community side had moved to Discord, and it meant nobody had to be told twice.
What Should You Test Before Trusting a Notification Scenario?
Trigger it with a real test event and confirm the message actually contains the details you expect, not just placeholder text or a broken variable. I once shipped a Discord alert that technically fired every time but displayed a blank field where the sender's name should have been, because I had referenced the wrong data point from an earlier module. It still counted as "working," it just was not useful, which is a trap worth checking for before you trust an alert with something time-sensitive.
Next step: Once your alerts are dialed in, the same webhook approach behind Discord notifications is worth understanding more broadly. Visit the automation hub for more Make.com guides, including how webhooks work under the hood.
