To add a bot to a Discord server, use Discord’s App Directory on desktop or in a browser. Open the server’s App Directory, choose an app, select Add App, choose server installation if Discord offers both contexts, review the requested permissions, and authorize it. You must own the server or have Manage Server.
After authorization, confirm that the app appears in the server member list or under Server Settings > Integrations > Bots and Apps. This guide covers permission review, mobile availability, commands, troubleshooting, removal, and the point at which a cross-service automation such as Zapier is a better fit. Discord labels and available surfaces can vary by client, account, and rollout.
How to add a bot to a Discord server
For a server feature such as a trivia command, install the app to the intended server rather than only to your Discord account. The shortest reliable sequence is: open the server on desktop or in a browser, open Server Settings > App Directory, select an app, choose Add App, select the server installation when offered, review permissions, and authorize. Then verify the app in the server.
If you do not own the server or have Manage Server, ask an authorized owner or administrator to review and install the app. Do not keep retrying authorization when the account lacks the required authority.
Know what you are installing before you authorize it
Discord uses app as the broader term. Bots are one type of app, and Discord may offer both account and server installation. These are different contexts. A server-installed app provides a server-level feature and can appear in the server member list. An account-installed app is not a substitute when the feature must operate for a server.
Compare the authorization screen with the app’s stated purpose. An app that only responds to a simple command may not need permission to manage roles, delete messages, create channels, or administer the server. Administrator should not be treated as a routine requirement. Discord’s official guide to using apps explains the current app workflow and installation contexts.
Use Discord’s App Directory as the authoritative discovery route. Third-party directories may list additional bots, but they are independent services. Review their permissions, privacy information, support details, and reputation separately rather than treating a listing as a Discord endorsement.
A permission request grants a capability. It does not prove that the app is trustworthy or that the capability is necessary.
Install the app from Discord’s App Directory
The documented App Directory workflow is intended for desktop and browser use. Discord’s authorization screen identifies the target and requested permissions before access is granted.
- Open the intended server and confirm that you own it or have Manage Server.
- Open Server Settings, then App Directory. Choose an app and read its overview.
- Select Add App. If Discord offers account or server installation, choose server installation when the feature must operate in the server.
- Check the selected server name. Compare the requested permissions with the app’s stated job.
- Select Authorize only if the target and permission scope are appropriate.
- Verify the result in the member list or at Server Settings > Integrations > Bots and Apps.
The integrations page helps administrators review what was added, who added it, when it was added, and the permissions requested by the app. See Discord’s guide to server integrations.
What to expect on mobile
Discord’s reviewed documentation describes the App Directory as available on desktop and in a browser, not as a universal mobile workflow. Mobile discovery and installation options can vary by client and account. If your iPhone or Android client does not show an install option, use Discord on desktop or in a browser for the documented App Directory flow, then verify the app in the server.
Do not rely on an old Discover-tab walkthrough as a guaranteed mobile process. Authorization steps may be similar when the current client exposes an installation flow, but the available discovery surface is not consistent enough to promise the same sequence on every device.
Check permissions, then try an app command
Permissions granted during installation are different from permissions needed to use an individual command. Open the App Launcher where available or type / in a channel where the app is permitted. Select a visible slash command, provide its required options, and submit it. Some apps also provide user or message commands through a context menu. Discord’s application-command documentation describes slash commands and other command types.
Command visibility depends on the app, channel, and user permissions. Start with a harmless command in a restricted test channel or private test server. Confirm the response or resulting change before relying on a higher-impact command. Do not assume that every app sends a welcome message or exposes a profile-based Commands section.
An app can appear in the server while a particular command remains unavailable. Test with the intended role and channel, supply only the required options, and record whether the command responds, changes the expected resource, or is blocked by a permission rule.
Troubleshoot a missing app or command
Diagnose the issue in order rather than repeating authorization or changing unrelated server settings:
- Authority: confirm that the installer owns the server or has Manage Server.
- Context: confirm that the app was installed to the intended server, not only to the user account.
- Record: look for the app in the member list and in Server Settings > Integrations > Bots and Apps.
- Command access: if the app is present but a command is missing, check whether the app supports it and whether the user and channel can use it.
If an unfamiliar app appears, or its permissions do not match its stated purpose, stop using it and ask the server owner or administrator to review the integration record. If the app is present but the command is unavailable, the issue may be command registration, app configuration, channel access, or user permissions rather than installation.
Remove a bot from the server
To remove a server-installed app, locate its bot in the server member list and kick it. You need to own the server or have the required server permissions. Confirm the bot’s identity before removing it, then check that it is gone from the member list. Discord’s supported method does not require the /kick chat command specifically.
Use Server Settings > Integrations > Bots and Apps to review the app and its requested permissions as part of the removal audit. Removing the bot removes the app from that server. It does not necessarily revoke a separate account-level authorization, so review that context separately if it matters to your account.
Use a Discord app or a cross-service automation?
Choose a Discord app when the capability must operate inside Discord through commands, roles, moderation, or another server feature. Choose Zapier when an event begins in another connected service and should trigger a documented Discord action. These are different operating models, even when both ultimately post in a Discord channel.
| Trigger or need | Optional AI job | Deterministic validation | Action and fallback |
|---|---|---|---|
| Discord-native command or server feature | None required | Confirm the command is visible to the user in the intended channel and that required options are supplied. | Run the app command. Test in a restricted channel first; send access issues to the server administrator or app maintainer. |
| New event in another connected service | Draft or categorize a short notification using a bounded output such as message text and needs-review status. | Require a source event ID, approved destination, permitted fields, valid message length, and an unused delivery key. | Use a documented Zapier Discord action such as Send Channel Message. Record rejected, duplicate, and failed events for the automation owner. |
For a cross-service notification, the proposed operational chain is: source event, selected fields, deterministic filter, optional bounded AI draft, validation and duplicate gate, Discord action, and operations review for failures. Zapier documents polling Discord triggers and actions including Send Channel Message. Check its current Discord integration guide and live editor for available events and fields. Because the triggers are polling triggers, do not promise instant delivery.
For example, a new forum-post event could produce a short notification in an approved Discord channel. Map only the fields needed for that notification, use a fixed destination, and preserve the source event ID, destination channel ID, final Discord message ID, delivery status, and error or retry state. Zapier’s documented connection process requires a Discord account, suitable server permissions, and Manage Webhooks in the relevant general-channel permissions. Those are Zapier connection prerequisites, not requirements for ordinary bot installation.
For event-level delivery records, define one row as one source event sent to one destination with one action. A proposed key is source_system + source_event_id + destination_channel_id + action_type. Use a database-enforced unique constraint or transactional upsert where concurrent runs are possible. A read-then-create check alone can race. If the source event ID is missing, route the event for review rather than deduplicating by date, channel name, or message text.
{
"source_system": "forum_service",
"source_event_id": "evt_illustrative_1042",
"destination_channel_id": "channel_illustrative_27",
"action_type": "send_channel_message",
"delivery_status": "pending_review",
"final_discord_message_id": null
}
This JSON is an illustrative event-delivery record, not a Zapier-published schema. Its row grain is one source event, destination, and action. A reported daily message count would be a separate aggregate and should not reuse this event key.
AI is optional. It can draft or categorize message text, but deterministic checks should validate the event ID, allowed fields, destination, content length, and duplicate status. Do not let an unconstrained model choose arbitrary channels, assign privileged roles, delete content, or expose personal data. Send uncertain or high-impact cases to a person.
Before enabling an automation, verify the destination is approved, the event has not already been committed, the message stays within the selected action’s limits, and any human-review rule is satisfied. If validation fails or delivery errors, record the failure for the automation owner instead of silently dropping the event.
