New on ClashScout: Send Each Discord Notification to Its Own Channel
War announcements in #war, applications in #recruitment, member joins in #general. You can now connect as many Discord channels as you like to one clan, each with its own set of alerts.
Updated 3 September 2026. Everything below still holds in principle, but the details have changed and improved. There are now seventeen alert types rather than six, setup happens inside Discord with
/notificationsrather than on the website, and an alert lives in exactly one channel rather than being switchable on in several. The current, accurate write-up is The ClashScout Bot Now Has 17 Alerts, and Each One Picks Its Own Channel. This post is kept as the record of when per-channel routing first arrived.
Until now, connecting your clan to Discord meant picking one channel and sending everything to it. War announcements, new applications, member joins and the daily digest all landed in a single stream, in whichever channel you happened to authorise first.
That was fine for a small server. For anyone running a properly organised Discord, it meant your #general filled up with recruitment noise, or your recruiters had to scroll past war reminders to find applications.
You can now connect as many channels as you want to the same clan, and decide separately what each one receives.
How It Works
Connect a channel from your dashboard, then decide what it should receive. Each channel is independent, so a typical setup might be:
- #recruitment for new applications
- #war for war announcements and war ending reminders
- #general for member joins and leaves
- #leaders for the daily application digest
Nothing is duplicated. A notification goes only to the channel you have chosen for it.
At the time of writing there were six notification types: new applications, member joins and leaves, war announcements, war ending reminders, the daily application digest, and player match alerts. That list has since grown to seventeen, and the current set is covered in the September post.
Two Things Worth Knowing
New channels start empty. When you connect an additional channel, it begins with nothing routed to it rather than everything. That is deliberate. If additional channels inherited the defaults, connecting a second one would silently double every notification into both places. Switch on only what that channel is for.
One alert, one channel. Sending the same alert to two channels only ever produced duplicate posts, so it is no longer possible. Switching an alert on in a new channel moves it there.
Changing It Later
Run /notifications in your server. You will get a channel picker and a list of every alert, with the ones that channel already receives already ticked. You need the Manage Server permission.
When this post was first written, that command worked differently: it took type and state options and applied to whichever channel you ran it in. It is now a panel, and it can set up a channel that has never been connected, because the bot creates the webhook itself.
Not Set Up Yet?
If your clan is not connected to Discord at all, the whole thing takes about a minute, and you will need to be a verified leader or co-leader of the clan first. Head to your dashboard to connect, or read more about what ClashScout offers clan leaders.
And if you are still recruiting the members to fill those channels, make sure your clan is listed as recruiting so players can actually find you.