Plan Discord events with RSVPs and reminders

The Events & Reminders module is available on Pro. Set a default channel, event manager role, reminder offsets up to two weeks and timezone in the dashboard. Member reminder opt-ins and native Discord event sync are both optional and off by default; each applies only to new events.

What you get

Example commands

Full command list and configuration options in the Events & Reminders documentation.

Your first event: setup, RSVPs and a full waitlist

1. Configure your server. Enable Events & Reminders on a Pro bot, regenerate it and start it. Open the module’s Settings in the bot dashboard and select your server. Choose #game-night as the default event channel, Europe/London as the timezone and 20160, 60, 10 as the reminder offsets in minutes. 20160 is two weeks. If you want members to choose reminders separately from RSVP, switch on Let members opt in to reminders before creating an event; it is off by default. Save your settings. The optional event manager role can cancel other organisers’ events and select a reminder role; it is not required just to create an event.

2. Check the channel permissions. Use an ordinary text or announcement channel. You need View Channel and Send Messages there. The bot also needs Embed Links, Attach Files and Read Message History. Keep the bot online so it can post events, refresh responses and deliver reminders and summaries.

3. Create Game Night. In Discord, choose /event create and fill in title: Game Night, time: YYYY-MM-DD 19:00 (replace the date with a future date), timezone: Europe/London, channel: #game-night, capacity: 2, duration: 120 and repeat: weekly. Duration is in minutes. Daily and monthly repeats are also available; choose none for a one-off event. Discord displays the posted time in each member’s local timezone. Check the post’s time and save the event ID shown in its footer.

4. Try all three responses before the start. Members click Going, Maybe or Can't on the event post. Clicking the same response again clears it. For this example, Alex and Sam click Going, Jo clicks Going next, Lee clicks Maybe and Pat clicks Can't. The post shows Going (2/2), Maybe (1), Can't (1) and Waitlist (1), with the members listed under each choice. Jo is on the waitlist, not in a confirmed place.

5. Free a place. If Sam changes to Can't, Jo moves from the front of the waitlist into Going. The example now shows Going (2/2), Maybe (1), Can't (2) and Waitlist (0). Reminder messages mention Going members unless an event manager chose a role to mention instead. If member opt-ins were enabled when this event was created, its Remind me button lets a member add or remove themselves from channel reminders without changing their RSVP. The role option controls mentions and takes priority over opt-ins; it does not grant anyone a role. RSVPs close at the event’s start.

6. Read the end summary. After this two-hour event ends, the bot posts an RSVP summary and a CSV attachment named event-<event ID>.csv. For the example above, the summary is “RSVP summary: 2 Going · 1 Maybe · 2 Can’t · 0 waitlisted. The CSV records RSVPs, not verified attendance.” The CSV begins with user_id,rsvp and lists Discord user IDs with going, maybe, cant or waitlist. These are responses, not verified attendance. The names and counts here are an illustration, not a live event record.

7. Check the next occurrence or cancel. After the event ends and its summary is delivered, a weekly repeat gets a new post with fresh, empty Going, Maybe, Can't and Waitlist lists. Members must respond again. Use /event list to find the current event ID, then /event cancel with that ID to cancel it and stop further repeats from it. The organiser, a member with Manage Server or the configured event manager role can cancel. If the previous occurrence has already ended, use the new occurrence’s ID.

Want a role that expires after Game Night? An authorised organiser must grant it separately with Temporary Roles. Events does not automatically assign attendee roles, verify attendance or sync a Google Calendar.

Optional native sync. Enable the dashboard toggle before creating an event. Previously created events are not imported. Grant Create Events to the organiser and bot; the bot manages only its own native events. Native events link to the source channel and are visible server-wide, so private source channels are rejected. Repeats create separate native events after the previous occurrence ends and its summary is delivered, not a Discord recurrence rule.

Edit and recover. Use /event edit id:<event ID> title:<new title> before the start; the bot post and native title are updated. Start time and duration are unchanged. Synchronization retries about once a minute while enabled, including after permission restoration and bot restarts. /event status shows failures and a link when an ID is known. The bot starts and completes native events at the scheduled times; cancellation closes a scheduled native event or completes an active one. Deleted or manually closed native events are not recreated. Discord edits do not change bot RSVPs.

Pause carefully. Turning sync off pauses native changes, including cancellation, and leaves existing native events in Discord. Re-enable it to resume. If a source channel becomes private, new details stop syncing but existing native details remain visible; cancel the event while sync is enabled if it should be closed. Native syncing does not copy Discord Interested counts into Going, Maybe, Can’t or the waitlist.

What does it cost?

Events & Reminders is included in Pro — Start free. Pro is $9.99/month.

Frequently asked questions

Related modules