English
日本語English简体中文暂无翻译，前往中文首页EspañolSin traducción: ir al inicio en español

If this page is not translated, the link opens that language’s home page.

Discord

Remove a Discord Bot or App: Account Access, Webhooks and Remaining Posts

For desktop/browser server administrators and account owners removing an app, revoking authorization or investigating posts/commands that remain afterward.

Edited by Gemnao Editorial Team (Japanese)Last checked 2026-10-18
Saved articles →
No account needed. Saved only in this browser.

The short answer

Identify the app’s responsibilities and preserve needed settings first. Remove a server bot from its server; deauthorize a personal app under Authorized Apps. Record the removal time. New posts may come from a separate webhook, followed channel or another member’s account-added app; old messages alone do not prove the bot is still installed.

Different symptom or still not fixed? Find the next check →

Key facts

Before routine removal
Plan for verification, role assignment, logs or scheduled posts that will stop
Different scopes
Server Integrations and your Authorized Apps are separate
Compare timestamps
Distinguish historical messages from posts created after removal

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
Bot appears in server Members/IntegrationsRemove the identified server installation after preparation.Step 2
App appears in your Authorized AppsRevoke your account authorization separately.Step 3
The same app exists in both listsChoose the intended scope; one removal does not establish both.Step 2
Bot is absent but new automatic posts continueIdentify webhooks and followed channels by destination/time.Step 4
Posts follow another member’s commandInspect their account-added app and server usage controls.Step 5
Only old posts or candidates remainDistinguish history/discovery display from current registration.Step 5

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1｜Preserve needed settings and plan for stopped functions

For routine cleanup, replacing a verification/role bot’s responsibilities first prevents new members being stranded.

Time: Compare one change at a time

  1. Match the server, bot identity and provider profile. Inspect its registration under Server Settings → Integrations.
  2. Identify active joining verification, role assignment, moderation logs and scheduled posts. Arrange alternatives for the functions actually in use.
  3. Record necessary destinations, roles and settings, using a provider export if available. Re-adding does not guarantee restoration of old configuration.
  4. Stop relevant scheduled posts/notifications in an external dashboard if present. Record the intended target and removal time.

If suspicious posting is actively occurring, prioritize stopping the identified source over a lengthy routine cleanup. Keep webhook URLs and tokens out of public notes or screenshots.

Results that did not fix the problem help the next reader too.

Step 2｜Remove the identified server bot and verify registration

On desktop, right-click the bot in Members and use Kick with confirmation. An app-specific removal control may also be available under Integrations.

Time: Compare one change at a time

  1. Recheck the bot name and server in the confirmation before executing the intended removal, then record the time.
  2. Reopen Members and Server Settings → Integrations and confirm the target entry is gone. An Offline label is not evidence of removal.
  3. If the control is absent or fails, ask the owner. App-management access and a member kick’s permissions/role hierarchy both matter; do not rearrange unrelated roles to force it.
  4. If the same app is authorized on your account, inspect Step 3 for that separate scope. If new posts continue, use Step 4.

This removes the installation from the selected server, not every server where that provider’s bot exists.

Results that did not fix the problem help the next reader too.

Step 3｜Deauthorize an app on your own account

Open User Settings → Authorized Apps and use the target’s Deauthorize control; labels can vary with language/version.

Time: Compare one change at a time

  1. Read the app/provider and granted access before revoking it. This is distinct from the Connections screen used for services such as Spotify.
  2. Reopen Authorized Apps and confirm the target is gone. A remaining server installation needs its own administrator action in Step 2 if that scope should also stop.
  3. If absent, do not remove a different app in its place. Another member’s account-added app requires their own account settings or appropriate server usage controls.

Results that did not fix the problem help the next reader too.

Step 4｜For new posts after removal, identify the webhook or forwarding source

Compare post time with removal time first. Existing history is not proof of continued execution.

Time: Compare one change at a time

  1. Record each new message’s channel, timestamp, displayed sender and link. Investigate messages genuinely created after the recorded removal.
  2. Open Server Settings → Integrations → Webhooks and compare destination channel, creator and creation time. A matching display name alone is insufficient identification.
  3. If matched to an external notification service, stop that sending configuration. Remove only a webhook confirmed no longer needed. Do not assume the same URL can be restored: recreating it requires configuring the new URL at the sending service.
  4. If messages are forwarded announcements from another server, inspect Channel Following in Integrations and remove only the unwanted source.
  5. At the next normally expected notification, check whether new posts cease. If another arrives, use that new message to investigate another webhook, bot or user-triggered app.

A webhook is a separate posting route. Removing a bot does not establish that every separately configured route has stopped. If the source cannot be identified, give the records to the administrator.

Results that did not fix the problem help the next reader too.

Step 5｜Treat remaining commands, history and roles separately

Hiding a candidate, stopping future posts and cleaning past history are different tasks.

Time: Compare one change at a time

  1. For remaining command candidates, reload Discord and match the app name against server and account registration. App Launcher also shows discoverable/recommended apps; visibility there alone does not prove reinstallation.
  2. If another member’s interaction produces replies, inspect account-added app use. Administrators can review Use External Apps under Server Settings → Roles → Apps Permissions and relevant channel overrides.
  3. To restrict public external-app replies, adjust only the intended role/channel permission. Private replies to the invoking user may remain available; this is not deleting their account-installed app.
  4. For historical posts only, preserve necessary logs before an authorized administrator removes unwanted messages separately.
  5. For leftover roles/channels, inspect members, access and other functions still using them before targeted cleanup. A matching bot name alone is not sufficient reason to delete them.

Results that did not fix the problem help the next reader too.

Avoid

  • Do not delete all webhooks, roles or channels just because the bot name matches.
  • Do not expose webhook URLs/tokens or assume re-adding restores provider-held data/settings.

Important cautions

  • Give the administrator the app/server identity, removal screen/time, current list entries and new message links/times. With suitable access, audit-log records can help identify bot/kick/webhook changes.
  • Provider dashboards and stored data have their own controls; server removal does not erase all historical messages or external data.

FAQ

Must I ban a bot to remove it?

Routine removal can use Kick or the available app removal control. Banning additionally restricts rejoining and serves a different purpose. Re-adding does not guarantee old settings return.

I deauthorized it, but the server bot remains.

Your account authorization and the server installation are separate. The server owner/authorized administrator must remove that installation if it should also stop.

Does removal erase every message and provider-held record?

No. Historical posts and externally stored data are separate. Preserve needed logs, use authorized message cleanup, and follow the provider’s data-removal guidance where relevant.

Can I undo webhook deletion?

Do not assume the old URL can be recovered. A recreated webhook needs its new URL configured at the sending service. Identify active dependencies before deleting the target.

Sources

English adaptation of the existing Japanese article. Official documentation supports the described controls and limits; comparison sequences are editorial guidance rather than measured results. Follow the permissions of the actual device, account and server, record original settings and verify the outcome before making another change.

Discord: using, adding and removing appsDiscord developer documentation: permissions and role hierarchyDiscord: moderating external apps and private repliesDiscord: integrations, webhooks and followed channelsDiscord: webhooksDiscord: roles, kick permissions and hierarchyDiscord: account protection and Authorized AppsDiscordJapanese version of this page