Discord bot ideas: 12 bots that work without reading anyone's messages

01 A scheduling poll that closes itself

Type /when with a few time slots; members tap buttons for the ones they can do, and the poll closes and announces the winner at the deadline.

Feature

Slash command, buttons, a timer on your server.

Good for

Raid groups, study groups and clubs that argue about Thursday.

Time to first version

A weekend.

Hard part

Editing the poll after the 15-minute interaction token has expired.

A post on the board asks for a group poll that closes itself. In Discord, buttons are interactive components, and each press arrives as an interaction your bot must acknowledge within three seconds. See the idea.

The catch is time. The interaction token is valid for 15 minutes, so a poll that closes tomorrow must be edited with the bot's own credentials, not the token. Store the message ID and the deadline, and check a timer every minute. First version: up to five slots, one vote per person, a result message. Extension: create a scheduled event for the winning slot.

Build a Discord bot in TypeScript using slash commands and buttons only. Do not use the message content intent.
User: a gaming group choosing a time.
Command: /when closes:<hours> slot1 ... slot5 (slots are text).
Behavior: post one message with a button per slot. A member can press several buttons; pressing again removes the vote. Show the counts and who voted on the message. When the deadline passes, edit the message to show the winner and post a mention of everyone who voted for it.
Data: SQLite with message id, deadline, votes.
Do not build: web dashboard, accounts, reminders.
Done when: with three slots and two voters choosing slot 2, the closed message names slot 2 and mentions both.

Read “A scheduling poll that closes itself” on the board and copy its build prompt →

02 Recurring game night as a real Discord event

A command that creates a repeating server event for game night and pings the interested members an hour before.

Feature

Guild Scheduled Events with a recurrence rule.

Good for

Weekly sessions of any game, book club or watch party.

Time to first version

A weekend.

Hard part

Time zones and the rules for recurrence.

Discord's scheduled event object includes a recurrence_rule that defines how often the event repeats, and an API to list the users who marked themselves as interested. That is everything this bot needs, and members use Discord's own event screen.

First version: /gamenight game:<name> day:<weekday> time:<HH:MM> creates the event; a timer pings interested users one hour before. Extension: a /skip command for a week off. Store the server's time zone once, and show the time in the reply so a mistake is obvious at once.

03 Which of my friends already owns this?

A /owns command with autocomplete that shows which opted-in members have a game, so the group can pick one everyone can play.

Feature

Slash command with autocomplete.

Good for

Friend groups deciding what to play on Friday.

Time to first version

One week.

Hard part

Getting a game list per person without asking for passwords.

A post on the board describes the question. Discord's autocomplete lets a string option suggest values as the user types, which is how a game title is picked from a list. Autocomplete cannot be turned on if the option has fixed choices. See the idea.

Start with no outside service: each member adds games with /iown, and /owns shows the overlap. That is useful already, and it avoids sensitive logins. Extension: import from a public profile if the member opts in and the store's terms allow it. Add /forget so a member can delete their list.

Read “Which of my friends already owns this?” on the board and copy its build prompt →

01 Rules lookup with autocomplete for a tabletop game

Type /rule and a few letters, pick a rule from the list and get the short text with a page reference.

Feature

Slash command, autocomplete.

Good for

Game masters and players who flip through a book mid-session.

Time to first version

A weekend.

Hard part

Using only text you have the right to share.

The data is the work. Use a rules document that is published under an open license, or rules you wrote yourself in your own words, and never paste a commercial rulebook. The bot is a search box over a file.

First version: a JSON file of 100 rules with a name, a two-line summary and a source note. Autocomplete returns the best five matches as the user types. Extension: /house-rule add so the group keeps its own changes, with an owner role who approves. Test misspellings; players do not type grapple the same way twice.

02 Save to FAQ from a message

Right-click a good answer, choose Save to FAQ, and it joins a searchable list the whole server can query.

Feature

Message context menu command, modal.

Good for

Support and community servers that answer the same question weekly.

Time to first version

A weekend.

Hard part

Keeping the FAQ current when answers change.

Message commands appear on the right-click menu of a message and return that message. A modal then asks for a short question title. Save the question, the answer text, a link to the original and the date. The bot reads only messages a moderator chose to save.

First version: moderators only, /faq query:<text> with autocomplete over titles. Extension: a stale flag after 90 days and a button on each entry for Still correct. This is a good example of why the privileged intent is not needed: the bot sees exactly the one message a person pointed at.

03 Translate this message, privately

Right-click a message in another language and get a translation only you can see.

Feature

Message command, ephemeral reply.

Good for

International communities and game servers.

Time to first version

A weekend.

Hard part

Translation quality and the cost of the translation service.

An interaction response can set the ephemeral flag, so only the person who ran the command sees the result. That keeps channels clean and avoids the bot talking over a conversation. Set the target language from the user's locale, which arrives with the interaction.

First version: one translation service, the user's own locale as the target and a hard cap on message length. Extension: a Show everyone button for when the translation helps the whole thread. Because each use sends a message to a third-party service, say so in the bot's description and privacy page.

04 Intro cards from the user menu

New members write a short intro once; right-click anyone and choose Intro to see their card.

Feature

User context menu command, modal.

Good for

Large servers where nobody knows who is who.

Time to first version

A weekend.

Hard part

Moderation of what people write on their cards.

A user command returns the user you clicked. The bot looks up that person's card and replies privately. The member edits their own card with a /intro command that opens a modal with three fields: what they play, their time zone and one fun fact.

First version: three fields, a private reply and a report button that pings moderators. Extension: a prompt in the welcome channel for new members. Keep cards short with strict field limits, and let members delete their card at any time.

01 Async standup with a form

A button opens a three-question form; at a set hour the bot posts everyone's answers in one thread.

Feature

Button, modal, scheduled post.

Good for

Remote teams and open-source projects across time zones.

Time to first version

One week.

Hard part

Showing who has not answered without nagging.

Modals are Discord's pop-up forms, opened as a response to an interaction. Three short text inputs fit the standup: done, doing, blocked. The bot stores answers until the posting time, then sends a single message with one section per person.

First version: one channel, one posting time and a /standup command that opens the form. Extension: a quiet reminder to people who have not answered by two hours before posting, and a weekly summary. Keep it opt-in so a standup does not feel like surveillance.

02 Bug reports that become forum posts

A /report command opens a form and creates a tagged post in a forum channel, so reports stay organized.

Feature

Slash command, modal, forum channels with tags.

Good for

Indie game and app communities.

Time to first version

One week.

Hard part

Duplicate reports.

Forum channels hold one post per topic, and Discord's channel docs define a forum tag object for labels. The form asks for a title, what happened and what the user expected. The bot creates a post with the Needs triage tag.

First version: three form fields, a forum post, and a reply that links to it. Extension: autocomplete on existing report titles to catch duplicates before the form opens, and a staff-only command to change the tag. Ask for the game version in its own field; it is the most useful line in any report.

Build a Discord bot in TypeScript using slash commands and modals only. Do not use the message content intent.
User: players of a small indie game.
Command: /report opens a modal with Title (max 90), What happened (paragraph, max 1000), Game version (max 20).
Behavior: create a post in the configured forum channel with the Needs triage tag, include the three fields and the reporter's mention, and reply privately with a link to the post.
Command: /status post:<autocomplete> status:<choice>, allowed only for members with the Staff role, changes the tag.
Do not build: database, web page, DMs.
Done when: a report with all three fields creates a tagged post, and /status by a non-staff member is refused with a private message.

03 Role menu with roles that expire

A select menu where members pick event or interest roles, and the bot removes event roles automatically after a set number of days.

Feature

String select menu, role management.

Good for

Servers with temporary groups: tournaments, jams, study weeks.

Time to first version

One week.

Hard part

Role permissions and the bot's position in the role list.

Select menus are interactive components that offer a list of options in a message. Each choice maps to a role. The twist is expiry: the bot stores the time each role was added and a daily job removes event roles older than the limit.

First version: one menu with up to ten roles, three marked as temporary with a seven-day limit. Extension: a /my-roles command and a reminder a day before expiry. A bot can only manage roles below its own highest role, so check the order first when it fails to assign one.

04 Daily check-in streaks without reading chat

One button per day logs a check-in for a habit or study goal, and a leaderboard shows streaks.

Feature

Buttons, slash command.

Good for

Accountability servers for studying, exercise or writing.

Time to first version

A weekend.

Hard part

What counts as a day across time zones.

Most check-in bots read messages to detect a post. This one does not: the button is the check-in, so the bot never needs the message content intent. A day is defined by each member's chosen time zone, stored once.

First version: a pinned message with a Check in button, a /streak command and a weekly top-ten post. Extension: a grace day each month. Decide up front what a missed day does and show it, because a surprise reset ends a streak and a member's trust together.

05 Weekly digest posted by webhook, no bot at all

A scheduled script posts a formatted summary of the week's merged pull requests, closed tickets or new members to a channel.

Feature

Webhook execution.

Good for

Teams and open-source projects that want a Friday summary.

Time to first version

A few hours.

Hard part

Keeping the webhook URL secret.

Discord's webhook resource lets a script post to a channel by URL, and it also documents Slack-compatible and GitHub-compatible endpoints. There is no bot user, no gateway connection and no server to keep running: a scheduled job on any host is enough.

First version: a script that reads your project's API for the week and posts one embed. Treat the webhook URL as a password: anyone with it can post to the channel. Extension: separate embeds per area and a link to the full changelog. Do not post customer names or emails.