Discord Server Removed You: Get Notified

This guide shows you how to set up a notification so you know the moment a friend group server removes you on Discord. Since Discord does not send a native alert for this, you will use a free third-party bot that watches the server’s member list and messages you when your name disappears. You will need the server’s invite link and permission to add a bot to that server.

What You’ll Need

Discord account with the friend group server you want to monitor
An invite link for that server (or the ability to generate one)
Permission to add a bot to the server (Manage Server permission)
A free account on a bot-hosting service like UptimeRobot or a self-hosted bot if you prefer

Step-by-Step

Create a bot on the Discord Developer Portal. Go to discord.com/developers/applications, click “New Application,” name it something like “Member Watcher,” and go to the “Bot” tab. Click “Add Bot” and copy the token (keep it secret).
Invite the bot to your friend group server. In the same portal, go to “OAuth2” > “URL Generator.” Select the “bot” scope and the “View Channels” and “Read Message History” permissions. Use the generated URL to invite the bot to the server.
Get the server and channel IDs. Enable Developer Mode in Discord (Settings > Advanced). Right-click the server name to copy its ID, and right-click the text channel where you want alerts to copy that ID too.
Set up a free monitoring service. Go to UptimeRobot.com, sign up, and create a new monitor. Choose “Keyword” as the monitor type.
Configure the keyword monitor. For the URL, enter the Discord API endpoint: https://discord.com/api/v9/guilds/YOUR_SERVER_ID/members?limit=1 (replace YOUR_SERVER_ID). Set the keyword to your own Discord username (case-sensitive).
Set the alert condition. Choose “Keyword doesn’t exist” as the alert trigger. This means the monitor will alert you when your username is no longer found in the member list.
Set the check interval. Choose the shortest interval available (usually 5 minutes on the free plan). This is how often the service checks the server.
Add alert contacts. In the monitor settings, add your email or Discord webhook as the alert contact. If you use a Discord webhook, create one in your server (Server Settings > Integrations > Webhooks) and paste the URL.
Start the monitor. Save the monitor and wait for the first check. If you are still in the server, the monitor will show “Keyword exists” and stay quiet. The moment you are removed, it will trigger and send you the alert.

Common Mistakes

Using the wrong keyword. The monitor matches your exact username, including capitalization and discriminator (e.g., “CoolGuy#1234”). If your username has a nickname on that server, use your global username instead.
Wrong API endpoint. The URL must have the correct server ID. A wrong ID returns an error or a different server’s data, which makes the monitor useless.
Bot not in the server. If the bot is not actually in the friend group server, the API returns a 403 error and the monitor will never work. Double-check the bot’s role and that it was invited successfully.
Alert contact not verified. On UptimeRobot, you must verify your email or webhook before it can receive alerts. An unverified contact silently fails.

Tips

Use a webhook instead of email. A Discord webhook delivers the alert straight to a private channel you control, which is faster and easier to notice than an email.
Test the monitor. Temporarily remove yourself from the server (or have a friend remove you) to confirm the alert fires. Then rejoin and check that it stops alerting.
Keep the bot token safe. Anyone with the token can control your bot. Never paste it into a public chat or a GitHub repository.
Consider a self-hosted bot for instant alerts. If you are comfortable with code, a small Python or Node.js script using discord.py or discord.js can check every few seconds and DM you instantly. Free hosting services are limited to 5-minute checks.

Troubleshooting

Monitor shows “Down” immediately. Check the API URL. Open it in a browser while logged out of Discord; you should see a JSON error about authentication, not a 404. If you see a 404, the server ID is wrong.
No alert when you leave. Verify the keyword is exactly your username. Also check that the monitor’s status is “Up” (meaning it can reach Discord). If it says “Down,” the API is rejecting the request—likely a bad server ID or the bot was kicked.
Alerts every 5 minutes even though you are in the server. This happens when the keyword is wrong or the API returns an error. The service interprets an error as “keyword not found.” Check the monitor’s response log for the actual HTTP status code.
Bot got removed from the server. If a server admin removes your bot, the monitor will start failing. Re-invite the bot using the same OAuth2 URL, and it will resume working.

Frequently Asked Questions

Can I get notified without a bot or third-party service?
No. Discord does not send any notification when you are removed from a server. The only native way is to notice the server disappearing from your list, which is not a notification.

Will the bot alert me if I leave voluntarily?
Yes, the monitor will alert you the same way. It cannot tell the difference between you leaving and being removed.

Is this against Discord’s terms of service?
No. Using a bot to monitor a server’s member list is allowed. The bot only reads public member data that you already have access to as a member.

How fast will I know?
On the free plan of UptimeRobot, checks run every 5 minutes, so you could know up to 5 minutes after removal. A self-hosted bot can notify you within seconds.

Can I monitor multiple servers at once?
Yes. Create a separate monitor for each server, each with its own server ID and the same keyword (your username).

What if the server is set to private and the bot can’t see the member list?
The bot needs the “View Channels” permission. If the server restricts that to certain roles, the bot will not see the member list and the monitor will fail. Give the bot a role with that permission.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →